AnsweredAssumed Answered

Activiti Event Listeners are only executed when async job is acquired with same machine

Question asked by alirezamirian on Aug 13, 2017

According to activiti async executor design, async jobs are acquired periodically in each instance of engine.

I have two instance of engine in two applications, one of them has an event listener to captures a handful of activity events and inform clients about them. The problem is that timer activities (or any async job) are sometimes handled by the other application and therefore event listener doesn't execute for subsequent events.

Is there a solution to ensure an activiti event listener is always executed even when another instance acquires and executes an async job?