AnsweredAssumed Answered

Caching, process variables, multiple jvms

Question asked by imamchishty on Apr 30, 2012
Latest reply on May 2, 2012 by trademak
Lets say that I've created a variable called userId and this is available for spring beans:

For example:

<serviceTask id="userTask" name="userTasks" activiti:expression="#{userTask.findUsersAddress(userId)}" />

In the above example the userId would be automatically provided to the userTask spring bean.

Questions:

1. Each time userId is required is this variable obtained directly from the database? Or from a local cache, e.g. map?

2. If I have multiple JVMs is there a recommended mechanism to handle variables to keep them in sync.

3. If JVM1 adds a new variable is this only available locally or to all JVMs?

4. Any recommendation on ehcache or hazlecast integration. I.e. let the cache maintain the variables rather than activiti?

Outcomes