"ejb3workshop" wrote : | However with ClusteredXAConnectionFactory it seems that message is sent outside the transactional context. Rather frequently it happens that the message arrives at the next bean, but the persistence has't finnished. The messages are however distributed evenly across both nodes. |
This is a classic misconception with using XA. If you do something like: a) write a row in a DB b) send a message In an ejb and use XA to enlist both those operations in the same global tx, then on commit, you might expect a) to happen before b) right? Wrong. The XA spec makes no guarantees of the order or concurrency of when the two things occur. All it says is they will both happen. That's just the way XA works, nothing to do with JBM. So if you're application expects to find the row in the db when it consumes the message , that won't be guaranteed to work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157747#4157747 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157747 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
