Hi Rainer, So indeed, the whole point of tx2 and tx3 happening concurrently is that the processinstance should be locked (either pessimistically or optimistically) to isolate them. This is not a jBPM related issue, it is a very general issue of transaction isolation when you have to access a shared resource (in the jBPM case this resource is the process instance). So the point Sean is making is very true, but the point I am trying to make for user's reading this thread is that these two transactions *should* be isolated to avoid problems. If you break this isolation by starting transactions in custom nodes than you will most certainly not able to roll thing back if something goes wrong.
Which brings me to your second use case. I remember we had this discussion earlier and I clearly see your point. The fact that there is no easy solution for obtaining this, is not at all jBPM related (as we also already concluded). It is again a more general issue for which I think there is no general solution. So you will have to look at your particular case (like you did) and come up with the best solution. One possibility I think, is to have some kind of a compensation mechanism in case something goes wrong in the MDB handling the messages sent in state d or state f. But as I already said, this is why we are called software engineers, there is some thinking to do here ;-) Anyway even in this second use case the problem of the first use case (a race condition on the processinstance) exists, so you will also want to lock the processinstance. Now for the serious business... Ronald told you already I am the blonde one with D-Cups, so I won't go looking for them :-P Besides, I am attending the JavaPolis conference next week, and these blonde D-Cups are hard to find in such an audience ;-)) I think it is a little too early for Christmas wishes, so that will be something for later... Cheers, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911961#3911961 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911961 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
