[ http://jira.jboss.com/jira/browse/JBPM-1027?page=comments#action_12370445 ] Matthew Sandoz commented on JBPM-1027: -------------------------------------- We removed the code uncommented in version 1.5 of Join.java from Dec '06 and were able to get the tests to pass. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPM-1027?page=comments#action_12370558 ] Edward Staub commented on JBPM-1027: ------------------------------------ Matthew, If you chase the issues noted in the original comment-out, they lead to: BPEL-260 Which is about concurrency issues. In an asynch (Job-running) environment, the fix you removed doesn't appear to work in all cases anyway. See JBPM-983 for more info. The FORCE-lock doesn't cut it - if another thread has already read the token and tries to update it (including FORCE), they're hosed with a stale object when they commit or FORCE. But it may have some value in some cases - I don't know all the use cases. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPM-1027?page=all ] Tom Baeyens closed JBPM-1027. ----------------------------- Resolution: Done i can't reproduce this case. from the description in the forum and here, i don't have enough or the right info to start searching for the problem myself. FYI: note that StaleObjectException is an optimistic locking failure. it is not a bug, but it means that the transaction must be rolled back and be retried. this is an FYI as the locking mechanism still could contain bugs. but a stale object exception on itself doesn't mean it is always a bug. if you have more information, please reopen this case -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPM-1027?page=all ] Tom Baeyens updated JBPM-1027: ------------------------------ Fix Version/s: (was: jBPM jPDL 3.2.2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPM-1027?page=all ] Tom Baeyens reopened JBPM-1027: ------------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBPM-1027?page=comments#action_12375817 ] Matthew Sandoz commented on JBPM-1027: -------------------------------------- I dont know that I am ready to reopen this as I can't really provide additional information. I have to say though that it fails every time for me which is quite vexing. I don't know if there are environmental differences but it fails in my unit tests and whenever I try to run even simple flows as the enclosed from the web console. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira