AnsweredAssumed Answered

JobExecutorActivate configuration question

Question asked by badrisudheer on May 1, 2013
Latest reply on May 2, 2013 by jbarrez
In a clustered environment when there are 2 activiti engines configured with JobExecutorActivate to true (for load balancing purpose), I observed instances where JobExecutor thread from 2 nodes (engines) are trying to acquire Jobs at the same time and one thread ends up throwing following exception

SEVERE: Error while closing command context
org.activiti.engine.ActivitiOptimisticLockingException: TimerEntity[e3ca0cba-b1c1-11e2-9038-005056b90423] was updated by another transaction concurrently

So, Is there a way to configure JobExecutor to run on specific intervals like specifying a Cron Expression for Quartz ?