Eventually, the JMS code should give up and throw some sort of java.net.SocketException . This might take the O/S 3-5 minutes. Does this not eventually happen?
"Fire and forget" does not mean complete asynchronous operation. When you send a message, the operation will only return until the message is on the server (and persisted). "Fire and forget" means once the message is enqueued, you do not have to wait until it is processed. I'm not sure closing the firewalled ports in the middle of a socket connect is going to work. I don't think the firewall cares one bit if you have a socket connection or not, it can still block the traffic. You can get a stack trace and post it here. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855753#3855753 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3855753 ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
