topic Re: Exception when multiple activiti engines up and running in Alfresco Archive

Exception when multiple activiti engines up and running

ganeshr — Fri, 21 Jun 2013 07:18:18 GMT

Hi, I'm facing an issue when one of my process contains timer boundary events. Here is the description of my issue. I have 3 different standalone applications and 3 business processes, and in each of these applications activiti engine is up and running connecting to the same database. These appl

Re: Exception when multiple activiti engines up and running

mmaker1234 — Fri, 21 Jun 2013 11:46:03 GMT

My experience with the workflow engines shows that the demonstrated behavior is the most common one. Once the process definition is deployed in the DB the workflow engine works with, the process definition is "visible" to the engine regardless the manner, subject, or object that deployed it there.

Regarding the above, if the applications are different you shouldn't share the process definitions among them, i.e. you should not deploy them in the same DB. Probably the easiest way to avoid the problem is to use separate DBs (users, schemata) for the different applications/Activiti engines.

You could still try to configure your engines with different names for the different applications but from what I know about Acitviti I doubt this approach will work with it, although it works with some other engines.

Re: Exception when multiple activiti engines up and running

ganeshr — Fri, 21 Jun 2013 12:54:54 GMT

could you provide the details of how to configure the engines with different names, may be I will try that approach and will check if that works or not.

Re: Exception when multiple activiti engines up and running

mmaker1234 — Fri, 21 Jun 2013 15:59:18 GMT

There is a property of the <code>processEngineConfiguration</code> bean in the Activiti Engine configuration file (activiti.cfg.xml in this example):<code> <bean id="processEngineConfiguration" class="org.activiti.engine.impl.cfg.StandaloneProcessEngineConfiguration">
<property name="processEngineName" value="ActivitiEngineForApp1"/>
…
</code>Of course you can also set it at run-time.

Re: Exception when multiple activiti engines up and running

ganeshr — Sat, 22 Jun 2013 05:54:39 GMT

I will try the proposed approach and will check if that works.Thank you for providing response.