Job executor in process engine embedded in webapp

Hi there,

We have a web app with an embedded process engine and an activated job executor. But because in development multiple instances of process engine run on the many developer machines, we have cases when the process instance is started on one developer machine, but the job executor of another developer machine picks up jobs that would normally be addressed to the machine that started the process instance. This makes it hard to debug code and it, as well, produces some exceptions from time to time. What is the suggested approach to this? We have to keep the process engine embedded in the web app. I guess one option is to enable the executor on one single machine, but I am still wondering what are the other suggestions.

Thank you,


Hi @Cristian,

use a local database like H2 on the developer machines. Start using a central database when it comes to integration-/system tests.

Cheers, Ingo

1 Like