Job executed tens of thousands of times during daylight saving time

Camunda 7 Topics Discussion & Questions
1

Hello,

We have a process in which an intermediate time event (non-interrupting) is triggered at 48H which got executed tens of thousands of times (~80000) during daylight saving hour.
After the first couple of times it threw:

        java.lang.NullPointerException
                at org.camunda.bpm.engine.impl.db.entitymanager.cache.DbEntityCache.getCachedEntity(DbEntityCache.java:145)
                at org.camunda.bpm.engine.impl.db.entitymanager.cache.DbEntityCache.setDeleted(DbEntityCache.java:362)
                at org.camunda.bpm.engine.impl.db.entitymanager.DbEntityManager.delete(DbEntityManager.java:513)
                at org.camunda.bpm.engine.impl.persistence.entity.EverLivingJobEntity.init(EverLivingJobEntity.java:79)
                at org.camunda.bpm.engine.impl.persistence.entity.JobManager.reschedule(JobManager.java:98)
                at org.camunda.bpm.engine.impl.jobexecutor.historycleanup.HistoryCleanupSchedulerCmd.execute(HistoryCleanupSchedulerCmd.java:69)                at org.camunda.bpm.engine.impl.jobexecutor.historycleanup.HistoryCleanupHandler$1.execute(HistoryCleanupHandler.java:49)                at org.camunda.bpm.engine.impl.jobexecutor.historycleanup.HistoryCleanupHandler$1.execute(HistoryCleanupHandler.java:42)

After that we could see in the logs:

org.camunda.commons.logging.BaseLogger.logWarn ENGINE-14006 Exception while executing job 5ac528f9-99cc-11ea-a122-001a4a140319: OptimisticLockingException. To see the full stacktrace set logging level to DEBUG.

And then the task was triggered again.

We suspect that it has something to do with the daylight saving.

Could you please advise on how we could prevent this on happening in the future?
P.S. We’re using Camunda 7.12 on Tomcat and it’s database is on a PostgreSQL.

Thank you!

2

Have you tried upgrading the latest version of Camunda?

3

No, we didn’t try to upgrade the version.
We’re not sure if this is related to the daylight saving time or it is another issue that cause this?

We were planning on upgrading the version, but to be honest not in the near future.

4

Would you be able to upgrade just in order to see if that fixes the problem.
It’s very possible that if it’s bug in Camunda it may have already been solved.

5

Ok, we’ll try to upgrade the version.

In the meantime we found https://jira.camunda.com/browse/CAM-4866 and we’re wondering if it is still a known issue for the lastest version.

Thank you very much for your quick reply!