cancel
Showing results for 
Search instead for 
Did you mean: 

Jobexecutor setup in a clustered environment

c_arunrathnakum
Champ in-the-making
Champ in-the-making
Hi All,

I use JBOSS EAP 6.0.

My setup is that we have 3 servers which has activiti-rest.war up and running. I ve customized the rest war by adding the ProcessEngine build at deployment time.

Each time ERROR logs are getting printed by ActivitiOptimisticLockException.
The main intention is to reduce the logs.

The same copy of war is deployed in all the 3 servers.

As for now we dont have any impact on the application, since jobexecutor works on the locking strategy.

How can I handle the OptimisticLockexceptions?

Is it better to handle the Exceptions or to have a custom jobexecutor like Agito?
Or anybody has a better solution?

Thanks in advance,
Arun
6 REPLIES 6

trademak
Star Contributor
Star Contributor
Hi Arun,

Which Activiti version are you using?
Currently this exception is logged only on debug level.

Best regards,

c_arunrathnakum
Champ in-the-making
Champ in-the-making
Hi,

We are using Activiti 5.11. As for now this is in production. So version change cannot be applied.. Please help me with a workaround

trademak
Star Contributor
Star Contributor
You can always override the job executor with your own implementation. But the easier way would be to upgrade to Activiti 5.15.1 I think.

Best regards,

c_arunrathnakum
Champ in-the-making
Champ in-the-making
Hi Tijs,

Is it ok if I m making the changes in source of 5.11 to log the OptimisticLockingException at 'FINE' level?

jbarrez
Star Contributor
Star Contributor
Sure. It is lowered in recent versions of Activiti.

c_arunrathnakum
Champ in-the-making
Champ in-the-making
Thank you.. Smiley Happy