The reason is that the session stores messages sent in a transaction locally. It doesn't send them to the server until the commit (which never happens because the timeout forces a rollback).
1) connection.createSession(...); // enlists session in transaction 2) add messages to the session (it is transacted) 3) timeout 4) keeps adding messages to the session 5) When finished, try to commit (which would send the messages to the server), but the timeout forces a rollback In other words: A createSession() or commit() will fail if a timeout has occurred. A send will not, because it is not communicating with the server (it is just accumulating messages waiting for a commit). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3845760#3845760 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3845760 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
