If I remember rightly, the problem was due to the Spring JMS template doing some really nasty stuff like opening a connection for each message sent (or consumed - I can't remember). So if you're using Spring template with a standard JMS connection factory you're going to get these horrible effects (as well as poor performance). A workaround in JBoss should be to make sure you're using the JCA JMS managed connection factory (the thing at java:/JmsXA), rather than a standard connection factory and feed that to Spring. The JCA MCF caches connetions internally so it won't actually create a new one each time. See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossJMSRA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077226#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...