The problem I see is here:
| prodA.send(createTextMessage(sessionA, "A"));
| prodB.send(createTextMessage(sessionB, "B"));
|
prodA and prodB will both send Async, in parallel execution, since they use two distinct
Sessions.
TransactionImpl is not synchronizing some of its collections, as the whole thing was not
really planned for concurrency, what was an exception when playing with Joining as the
test was written.... creating some race conditions.
Those tests will aways fail in the first time, and pass at the second time. (probably
because of ClassLoading creating more race conditions).
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217221#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...