AnsweredAssumed Answered

Logging ActivitiOptimisticLockingException in Clustered Env.

Question asked by er3n on Jan 21, 2013
Latest reply on Jan 21, 2013 by 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 name="org.activiti.engine.impl.interceptor.CommandContext" >
      <level value="FATAL"/>

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

Thanks for help.

Eren Öztürk