Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-9454

History cleanup with removal configuration cause exceptions

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.10.0, 7.10.0-alpha6
    • 7.10.0-alpha5
    • engine
    • None

      Configure historyCleanupByRemovalTime.

      <property name="historyCleanupByRemovalTime">true</property> 
<property name="hierarchicalHistoryCleanup">false</property>
      • In case of Jboss server the engine cannot start because of loop of NPE:
      10:55:11,536 WARN  [com.arjuna.ats.jta] (job-executor-tp-threads - 2) ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.camunda.bpm.engine.impl.cfg.jta.JtaTransactionContext$TransactionStateSynchronization@84f625 with exception: java.lang.NullPointerException
	at org.camunda.bpm.engine.impl.jobexecutor.historycleanup.HistoryCleanupRemovalTime.isDmnEnabled(HistoryCleanupRemovalTime.java:67) [camunda-engine-7.10.0-alpha5-ee.jar:7.10.0-alpha5-ee]
	at org.camunda.bpm.engine.impl.jobexecutor.historycleanup.HistoryCleanupRemovalTime.reportMetrics(HistoryCleanupRemovalTime.java:77) [camunda-engine-7.10.0-alpha5-ee.jar:7.10.0-alpha5-ee]
	at org.camunda.bpm.engine.impl.jobexecutor.historycleanup.HistoryCleanupRemovalTime.execute(HistoryCleanupRemovalTime.java:47) [camunda-engine-7.10.0-alpha5-ee.jar:7.10.0-alpha5-ee]
	at org.camunda.bpm.engine.impl.cfg.jta.JtaTransactionContext$TransactionStateSynchronization.afterCompletion(JtaTransactionContext.java:104) [camunda-engine-7.10.0-alpha5-ee.jar:7.10.0-alpha5-ee]
	at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
	at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:402)
	at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:103)
	at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
	at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165)
	at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
	at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
	at org.camunda.bpm.engine.impl.interceptor.JtaTransactionInterceptor.doCommit(JtaTransactionInterceptor.java:118) [camunda-engine-7.10.0-alpha5-ee.jar:7.10.0-alpha5-ee]
	at org.camunda.bpm.engine.impl.interceptor.JtaTransactionInterceptor.execute(JtaTransactionInterceptor.java:70) [camunda-engine-7.10.0-alpha5-ee.jar:7.10.0-alpha5-ee]
	at org.camunda.bpm.engine.impl.interceptor.ProcessApplicationContextInterceptor.execute(ProcessApplicationContextInterceptor.java:66) [camunda-engine-7.10.0-alpha5-ee.jar:7.10.0-alpha5-ee]
	at org.camunda.bpm.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:30) [camunda-engine-7.10.0-alpha5-ee.jar:7.10.0-alpha5-ee]
	at org.camunda.bpm.engine.impl.jobexecutor.ExecuteJobHelper.executeJob(ExecuteJobHelper.java:47) [camunda-engine-7.10.0-alpha5-ee.jar:7.10.0-alpha5-ee]
	at org.camunda.bpm.engine.impl.jobexecutor.ExecuteJobHelper.executeJob(ExecuteJobHelper.java:40) [camunda-engine-7.10.0-alpha5-ee.jar:7.10.0-alpha5-ee]
	at org.camunda.bpm.engine.impl.jobexecutor.ExecuteJobsRunnable.executeJob(ExecuteJobsRunnable.java:88) [camunda-engine-7.10.0-alpha5-ee.jar:7.10.0-alpha5-ee]
	at org.camunda.bpm.engine.impl.jobexecutor.ExecuteJobsRunnable.run(ExecuteJobsRunnable.java:57) [camunda-engine-7.10.0-alpha5-ee.jar:7.10.0-alpha5-ee]
	at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
	at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:806)
	at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
	at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:847)
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_80]
	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
      • Wildfly 14 is starting and history cleanup ran but you can still see the exception from above in the log
      • Tomcat is starting but the history cleanup seems to not work correctly.

      Hint: In case of Jboss the Context.getCommandContext()[1] is null because it is not in a command. It is not clear why it behaves differently for the other servers.
      [1]: https://github.com/camunda/camunda-bpm-platform/blob/cc0fcd428dd1c17bd0126736a6d56d25115929b4/engine/src/main/java/org/camunda/bpm/engine/impl/jobexecutor/historycleanup/HistoryCleanupRemovalTime.java#L67

        This is the controller panel for Smart Panels app

              yana.vasileva Yana Vasileva
              yana.vasileva Yana Vasileva
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: