You don't seem to understand how Managed environments work. There is lots of wrapping to protect you from having to deal with the real resources and the "book keeping" involved
When you look up java:/JmsXA (or an alias of this using java:comp) you are not talking directly to the jms provider. You are talking to a pool that manages the underlying jms connections. The pool may not be able to satisfy your requests due to underlying failures (i.e. transaction rollback) but that is only for that request. The pool spots the failure and creates new connections internally for later requests (if that is possible). It is impossible to make failures transparent within a transaction. It is the nature of a transaction that they have state that cannot be recovered. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3868113#3868113 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3868113 ------------------------------------------------------- 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
