This looks like a bug to me. Clebert seems to have identified the problem - I think a fix should be fairly straightforward. We just nee to add a check in the code, something like this: | if (currentThread != messageListenerThread) | { | waitForOnMessageToComplete(); | } | else | { | //don't wait | } | BTW Todd in your code, there's no need to stop the connection, then close the consumer, session and connection, just doing a connection.close() will automatically stop and shut the session and consumers. This doesn't effect the validity of the bug though. Also if you are going to immediately acknowledge the message using message.acknowledge() you may as well use auto acknowledge. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970530#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...