Change caching strategy from nonstrict-read-write to transactional in hibernate configuration files to ease clustering of jBPM ------------------------------------------------------------------------------------------------------------------------------ Key: JBPM-2518 URL: https://jira.jboss.org/jira/browse/JBPM-2518 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Aleksander Adamowski Priority: Optional In Szymon Zeslawski's excellent article about clustering jBPM (http://www.theserverside.com/tt/articles/content/WorkflowEngineJBossClust...) much of its content is dedicated to making jBPM more cluster-friendly by overriding jBPM's default cache management strategy in its hibernate mapping files to be friendly to JBoss TreeCache (which doesn't support "nonstrict-read-write" - only "transactional"). Since AFAIK changing the strategy from "nonstrict-read-write" to "transactional" should not introduce problems, only make the behaviour more correct at a price of small performance hit, and it would enable clustering of jBPM, I suggest that the cache strategy should be changed in the jBPM sources globally for future releases. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira