[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1953) Select the Lock Strategy in jbpm.cfg.xml

[ https://jira.jboss.org/jira/browse/JBPM-1953?page=com.atlassian.jira.plug... ] Martin Putz commented on JBPM-1953: ----------------------------------- My previous statement regarding Issue 2 has proven to be wrong. As mentioned in JBPM-1952, there is still a problem with the bpm_orchestration2 quickstart if multiple JobExecutorThreads are around. I have not yet succeeded in creating a test case that reproduces this issue outside the ESB environment. Regarding Issue 2: Running the same ESB quickstart (simple jBPM process, 100 process instances created, 2 cluster nodes) with both jBPM 3.2.2+ and 3.2.5 showed that the chance of running into StaleObjectStateExceptions has been reduced in the newer jBPM version. But they *can* still occur. Therefore, as StaleObjectStateExceptions are considered "part of the normal operation" in jBPM3 under certain circumstances, such as having multiple JobExecutorThreads in a cluster, shouldn't we configure the SOA-P to hide these stack traces in the logs completely: 1. set log4j threshold for org.hibernate.event.def.AbstractFlushingEventListener to 'FATAL' 2. have a fix for https://jira.jboss.org/jira/browse/JBPM-1988 3. configure the transaction manager logging to suppress the 'WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_2]' message -- 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