topic Logging ActivitiOptimisticLockingException in Clustered Env. in Alfresco Archive

Logging ActivitiOptimisticLockingException in Clustered Env.

er3n — Mon, 21 Jan 2013 14:41:36 GMT

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

Re: Logging ActivitiOptimisticLockingException in Clustered Env.

frederikherema1 — Mon, 21 Jan 2013 14:46:39 GMT

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

Re: Logging ActivitiOptimisticLockingException in Clustered Env.

er3n — Mon, 21 Jan 2013 15:17:20 GMT

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.

Re: Logging ActivitiOptimisticLockingException in Clustered Env.

frederikherema1 — Mon, 21 Jan 2013 15:24:20 GMT

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

Re: Logging ActivitiOptimisticLockingException in Clustered Env.

er3n — Mon, 21 Jan 2013 15:31:15 GMT

Collection Management System for telecommunication companies.