> The JMS spec just says that all messages in a single tx are sent or not sent. > It says nothing about the timing of when they appear on the destination.
But it would make sense if all messages in the same transaction appear on the destination at the same time. In Fact I think it is what everybody assumes. It is a shame the spec is so lax in that respect. About the transaction isolation, your statement about the QueueBrowser does not apply. The SB uses a transacted MessageConsumer first and THAT does not see the messages that were in the same transaction as the one that triggered the MDB. About the global ordering. How can I ensure global ordering across multiple Sessions? I already make sure to send and commit in the right order. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866417#3866417 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866417 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
