Caching, process variables, multiple jvms

imamchishty — Mon, 30 Apr 2012 15:37:35 GMT

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 sprin

Re: Caching, process variables, multiple jvms

trademak — Wed, 02 May 2012 08:51:52 GMT

Hi,

1. It's cached inside the Activiti Engine.
2. If you have multiple JVMs it also should be no problem as-is. The Activiti Engine runs all the synchronous elements of a process definition in one go.
When for example a user task is encountered, the process state is stored to the database, including its variables.
Then when the user task is completed and the process instance continues, the process execution and variables are retrieved from the database or the cache.
3. It's available only on JVM1 at first, but when the process instance is persisted it's of course available to all JVMs.
4. Do you see performance issues for your usage? Activiti is pretty fast already, and is scalable to multiple JVMs out-of-the-box, so why would you want to add another cache?

Best regards,

topic Re: Caching, process variables, multiple jvms in Alfresco Archive

Caching, process variables, multiple jvms

Re: Caching, process variables, multiple jvms