You didn't need to dump the logging, I know exactly how it works. :-) The MC only has to maintain a one-one relationship with the *active* XAResource, that is why TM_SUSPEND exists.
JBossMQ handles transaction interleaving quite effectively, it allows fewer connections to be used for the same number of transactions. anonymous wrote : | As for the <track-connection-by-tx> attribute: it does work, but it is not compliant with the JCA specification | Configuration/deployment of the connection manager/pool isn't even in the jca spec so how can it a compliance issue? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842613#3842613 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842613 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
