This looks like an error in the MDB container or the resource adapter. The first error says the consumer can't deliver the message because the server session pool is not started: | I think the problem is fixed now. I changed the log4j dependency to point to the correct path. Log4j 1.2.14 was not in our repository, but it is in the central maven repository under /log4j/log4j. | What I don't see is an invocation of the ExceptionListener when it encounters this problem, instead it just logs a warning: | WARN 28-03 17:15:21,093 (JBossConnectionConsumer.java:run:303) -Connection consumer closing due to error in listening thread JBossConnectionConsumer[22, 1] | javax.jms.JMSException: Unable to get a server session java.lang.Exception: Cannot get a server session after the pool is stopped | which is useless for recovery. The rest of the log is NOISE that should not be there. Why log an error during close at ERROR level? It should be DEBUG at most, otherwise the user is not going to understand what the real problem is (in this case, it was already broken) - like Bill didn't, "Error closing a session" is not the problem it is a symptom. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032798#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...