Logging ActivitiOptimisticLockingException in Clustered Env.

[er3n]

Hi, When i display logs, i see thousands of;

org.activiti.engine.ActivitiOptimisticLockingException: TimerEntity[2839258963] was updated by another transaction concurrently
‍‍‍

  This is exceptions causes because of clustered enviorment and they are not worth considering for us.

To disable this log we added following lines in log4j configuration:

    <logger name="org.activiti.engine.impl.jobexecutor.JobAcquisitionThread" >
      <level value="FATAL"/>
    </logger>
    
    <logger name="org.activiti.engine.impl.interceptor.CommandContext" >
      <level value="FATAL"/>
    </logger>
‍‍‍‍‍‍‍‍‍

My question is: Is there more efficient way to turn off this logs?

Thanks for help.

Eren Öztürk

[frederikherema1]

If you want to remove the logging, I'm afraid the only solution is to higher the level to ERROR/FATAL. You could also look at the cause of the issue. Is it possible to run the job-executor only on one machine in the cluster? Because the AOLExceptions are cause by multiple job-executors acquiring the same jobs… Having multiple job-executors is perfectly fine off course, but you'll have to take the AOLExceptions that come with it

[er3n]

Thanks for quick replay.

Unfortunately it is not possible run the job-executor only on one machine. There is about 2 million jobs and their due date is almost the same.

[frederikherema1]

LOL… Okay, you're right. About 2 million jobs, that's a big setup. Do you mind sharing what project you're using Activiti for? Just curious

[er3n]

Collection Management System for telecommunication companies.