There is no such concept of transaction isolation in JMS (it could be done as a value added feature, but it isn't supported by JBossMQ).
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. Even if there were transaction isolation, the non transactional QueueBrowser would not necessarily be included in this behaviour. In fact, this is the only part of JMS that would require transaction isolation as it is the only part that gives you any form of view of the internal state of a destination. But since it is non transactional, transaction isolation is not required. The reason why it probably works with OracleAQ is you are talking to a special set of database tables when you use their JMS. The behaviour is implicit in their implementation. You are relying on a non-spec feature. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866262#3866262 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866262 ------------------------------------------------------- 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
