After reviewing the recovery logic in our app I believe that we are encountering a deadlock in the 'onException' method of our Queue Exception Listener.
Because we never set the exception listener to null when before closing the queue connection in our exception listener it triggers another JMSException (the queue is already closed - it got a EOF Exception). The onException method is invoked again, since the method is synchronized it blocks the caller which is JBoss and I believe that this prevents the PingTask from being stopped and so we continue to get Ping Timeouts. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862499#3862499 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862499 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
