[ https://jira.jboss.org/jira/browse/JBPM-1953?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1953: --------------------------------- Description: A StaleObjectStateException is thrown by Hibernate so easily, if the number of JobExceutor's thread is two or more. If you set the number of thread to ./samples/quickstarts/bpm_orchestration2, you could see the issue easily. For a complete description, see the (private) document attached to JBPM-1952 was: A StaleObjectStateException is thrown by Hibernate so easily, if the number of JobExceutor's thread is two or more. If you set the number of thread to ./samples/quickstarts/bpm_orchestration2, you could see the issue easily. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-1953?page=com.atlassian.jira.plug... ] Thomas Diesler commented on JBPM-1953: -------------------------------------- Only that a multi million dollar with a japanese telco depends on it ;-) More details are attached to JBPM-1952 -- 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

[ https://jira.jboss.org/jira/browse/JBPM-1953?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1953: --------------------------------- Priority: Major (was: Critical) -- 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

[ https://jira.jboss.org/jira/browse/JBPM-1953?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-1953: ----------------------------------- " Issue 1: A lot of StaleObjectStateException are thrown by Hibernate, if a jBPM process on SOA Platform run in a cluster. " ==> this is expected behaviour in a cluster. the user is in that case supposed to retry the operation. " Issue 2: A StaleObjectStateException is thrown by Hibernate so easily, if the number of JobExceutor's thread is two or more. If you set the number of thread to ./samples/quickstarts/bpm_orchestration2, you could see the issue easily. " ==> same thing. " Plan 1: Set the name to each JobExecutor's name field in jbpm.cfg.xml, if the system using SOA Platform is in multi-instances or in a cluster. By this plan, the name of each Job become unique. So, the rate of this fail by optimisticLoking would become small number. but it's not complete solution. There is still a possibility that the exception occurs. " ==> that is indeed a requirement to get job executors to run ok on multiple nodes. but it will not eliminate concurrent optimistic locking exceptions. " Plan 2: Use JMS instead of DBMS for the store of Jobs. " ==> that will create more problems then it solves. in fact, it will solve none. " Plan 3: Select Pessimistic lock. If the system can choose the lock strategy of JobExecutor like PessimisticLocking or OptimisticLoking, the system could choose the strategy in their environment. But it's a kind of enhancement request to jBPM/SOA Platform. " ==> pessimistic locking will not help either to get rid of exceptions. in a cluster, and with competing threads trying to perform transactional operations on single process instance, you'll always have transactions that have to roll back. even with pessimistic locking. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-1953?page=com.atlassian.jira.plug... ] Martin Putz commented on JBPM-1953: ----------------------------------- "Issue2: Workaround: Don't use ESB node in Fork/Join using jPDL." ==> To get around StaleObjectStateExceptions when entering a Join on certain databases (postgres, oracle), jBPM 3.3.x allows to alter the locking strategy of the parent token (see JBPM-1886). A quick test of running the bpm_orchestration2 quickstart (DB=postgres, nbrOfThreads=2, jBPM 3.3.0.GA) with a different locking strategy (<join name="join1" lock="READ">) resulted in successful runs without any errors. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-1953?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1953: --------------------------------- Fix Version/s: jBPM-3.2.5.SP1 -- 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

[ https://jira.jboss.org/jira/browse/JBPM-1953?page=com.atlassian.jira.plug... ] Mark Little commented on JBPM-1953: ----------------------------------- We are not going to configure the transaction manager to suppress warnings. The TM is correct in giving this warning and it does not have the necessary semantic information to disambiguate this Synchronization from a one that is really in error. The issue should be dealt with by the participant. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-1953?page=com.atlassian.jira.plug... ] Alejandro Guizar updated JBPM-1953: ----------------------------------- Fix Version/s: (was: jBPM 3.2.6 GA ) -- 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