well, the transition to a previously left node was in fact taken, but the task which was binded to this node was declared ended (by a taskInstance.cancel() ) as soon as we entered into the node. The default transition was immediatly fired. The SQL error came when comitting the transaction : the second node should be updated before being created (or somthing like that), that's why I had my deadlock (SQL error 1205). The deadlock prevents the transaction to be completed leading to a rollback. That's why I had the impression to stay in the same node. I removed the cancel of the task which had no reason to be here (and modified a bit the task to have the behaviour actually wanted by the users).
I hope it may help you, Eric View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939787#3939787 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3939787 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
