We have a Java listener that reads text messages off of a queue in JBossMQ. If we have to reboot JBoss, the listener will not reconnect and start reading messages again. We just get messages in the listener's log file every 2 minutes saying it can't connect. Is there something we're not setting in our code or in JBossMQ? I'm new to JMS so any help will be greatly appreciated. Thanks.

+3  A: 

You should implement in your client code javax.jms.ExceptionListener. You will need a method called onException. When the client's connection is lost, you should get an JMSException and this method will be called automatically. The only thing you have to control for is if you are actually trying to disconnect from JBossMQ that will also throw an exception. Some code might look like this:

    public void onException (JMSException jsme)
        if (!closeRequested)
            this.establishConnection(connectionProps, queueName, uname, pword, clientID, messageSelector);
            //Client requested close so do not try to reconnect

In your "establishConnection" code, you would then implement a while(!initialized) construct that contains a try/catch inside of it. Until you are sure you have connected and subscribed properly, stay inside the while loop catching all JMS/Naming/etc exception. We've used this method for years with JBossMQ and it works great and have never had a problem with our JMS clients not reconnecting after bouncing JBossMQ or loosing our network connection.

Note that one should use Connection#setExceptionListener (with some JMS providers at least) to register the ExceptionListener.
+2  A: 

I'd highly recommend you use the Spring abstractions for JMS such as the MessageListenerContainer to deal with reconnection, transactions and pooling for you. You just need to supply a MessageListener and configure the MessageListenerContainer with the ConnectionFactory and the container does the rest.

James Strachan
+2  A: 

If you're purely a listener and do no other JMS calls other than connection setup, then the "onException() handler" answer is correct.

If you do any JMS calls in your code, just using onException() callback isn't sufficient. Problems are relayed from the JMS provider to the app either via an exception on a JMS method call or through the onException() callback. Not both.

So if you call any JMS methods from your code, you'll also want to invoke that reconnection logic if you get any exceptions on those calls.

John M

Piece of advice from personal experience. Upgrade to JBoss Messaging. I've seen it in production for 4 months without problems. It has fully transparent failover - amongst many other features.

Also, if you do go with Spring, be very careful with the JmsTemplate.