Activiti timer process not starting on all the nodes

[irchowdary]

Hi,

I am working on an Activiti BPM process that has to start for every 5minutes; using timer event to start the process.

This is working good when deployed on one node using mysql activiti db, but when pushed it to an environment that has 2 nodes with both the nodes pointing to one mysql activiti db - it is not working as expected. It runs for every 5 minutes, either on node1 or node 2, but not on both.

I want to set this up in a way activiti BPM process runs on each node for every 5 minutes.

Could someone please share your thoughts on this?

Using Activiti 6.0 with SpringBoot and Mysql db.

We have not made any specific changes to the config, all the activiti properties are default configuration.

Thanks,

Ravindra

[cjose · Accepted solution]

Hi Ravindra,

The behavior that you seeing is the expected behavior, and is working as designed. With activiti, the timer job is created in the database and will be picked up by one of the nodes.

Since you are using spring-boot, you can achieve your requirement easily using @Scheduled (Getting Started · Scheduling Tasks ) annotation and start processes in each spring-boot application using the java apis - RuntimeService (Activiti - Engine 6.0.0 API) 

Hope this helps.

Regards,

Ciju

[irchowdary]

Thanks Ciju.

We made changes to start activiti processes using quartz scheduler and it is working as expected.