[ http://jira.jboss.com/jira/browse/JBESB-901?page=all ] Kevin Conner updated JBESB-901: ------------------------------- Fix Version/s: 4.2.1 triage (was: 4.2.1) -- 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/JBESB-901?page=comments#action_12384695 ] Kevin Conner commented on JBESB-901: ------------------------------------ It is jBPM specific, it is an error that it is produced when you have a recursive lock. We need to understand the implications of releasing the lock early though, which is why this is still open. -- 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/JBESB-901?page=comments#action_12386806 ] Tom Baeyens commented on JBESB-901: ----------------------------------- the motivation for token locking is that when e.g. an asynchronous continuation has to happen, we know that the job executor is expected to pick up the async message and continue the execution of the process automatically. then it would not be good if a concurrent transaction would perform an operation on that token, inbetween the production of the async message and the consumption by the job executor. therefor, we write the lock owner as a string in the token. the job executor will then unlock it. it could be that this logging appeared after fixing another problem. so that in fact it is just the log that is wrong. can you give more information about the situation. so that i can reproduce or look in the code ? HTH -- 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/JBESB-901?page=all ] Kurt Stam closed JBESB-901. --------------------------- Resolution: Done Fixed by making the interaction asynchronous. -- 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