Connection exception listener mechanism does not work with jboss-messaging-client 1.4.6.GA ------------------------------------------------------------------------------------------ Key: JBMESSAGING-1800 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1800 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.6.GA Environment: Fedora 12, JBoss AS 5.1.0.GA Reporter: Bozhidar Batsov Priority: Critical We recently upgraded the JBoss Messaging bundled with JBoss AS 5.1.0.GA (1.4.3.GA) to 1.4.6.GA. At this point the exception listeners that we employed to monitor JMS connections stopped working. The problems seems to be solely in the jboss-messaging-client library. // create a queue sender QueueSender queueSender = queueSession.createSender(queue); queueSender.setDeliveryMode(DeliveryMode.NON_PERSISTENT); queueConn.setExceptionListener(new ExceptionListener() { public void onException(final JMSException e) { System.out.println("JMS connection problem"); } }); For example if I have to primitive queue clients - a producer and a consumer and I shutdown JBoss AS, the connection exception listeners were immediately executed on both the consumer and the producer. But after the upgrade to 1.4.6 they don't get executed at all - on the consumer side I get some unhandled connection exception when trying to send a new message and on the consumer nothing happens at all. What makes this regression dangerous if the fact that a lot of people use code like this to automatically reconnect to JBoss Messaging on connection failures and this now simply doesn't work. I thought that this issue might somewhat to connected to the problem - https://jira.jboss.org/jira/browse/JBMESSAGING-1776 , I applied manually the fix to the 1.4.6.GA tagged code, but it doesn't help so it probably fixed something else. For the time being our project has switched back to the working jboss-messaging-client 1.4.3.GA, while using 1.4.6.GA on the server side. I hope to hear at least some suggestions or comments on this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira