Ok, here's some more info on my problem: I tested the lock with 2 thin clients accessing the same application server running jBPM and the lock didn't work. When I tested 2 thin clients accessing different applications servers, it worked, I couldn't load the process definition in server2 while server1 was still executing. But after server1 finished, server2 executed the process definition normally. I read somewhere in the forums that it should have rollback. What is correct?
And I still have the problem that if I use 1 AS with jBPM, any 2 clients can run the same process definition, even though it was locked. Is this really the correct behavior? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928580#3928580 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3928580 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
