I spend a good part of the day today analyzing http://jira.jboss.com/jira/browse/JBMESSAGING-721 and its implications (which include http://jira.jboss.org/jira/browse/JBMESSAGING-410 and http://jira.jboss.org/jira/browse/JBMESSAGING-520) On one hand, the fixes for JBMESSAGING-410 and JBMESSAGING-520 insure that a JMS session created using a JMS connection produced by the JCA connection factory behaves as NON-TRANSACTED in absence of a global JTA transaction. This is an intuitive behavior, users rely on it, JBossMQ behaves similarly, and reportedly, other JMS providers as well. Unfortunately, the fix caused http://jira.jboss.com/jira/browse/JBMESSAGING-721. Reverting it would fix MDB redelivery problem, but it will break JBMESSAGING-410 and JBMESSAGING-520 again. At this moment, I am tempted to blame JCA and say that the fix for JBMESSAGING-410 and JBMESSAGING-520 belongs to the JCA layer. However, users don't see JCA, they see JBoss Messaging not working as expected. I haven't reached a definitive conclusion yet, I will continue thinking about this issue tomorrow. In the mean time, the fix for http://jira.jboss.org/jira/browse/JBMESSAGING-748 is badly needed at some production sites, so I will release a partial service pack (1.0.1.SP3) but not make it available for public consumption, pending a resolution on JBMESSAGING-721, which will be incorporated in 1.0.1.SP4. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003163#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...