anonymous wrote : In both options its the end-point proxy that controls the transaction -- see Figure 12-7 in JCA 1.5. The end-point could be a MDB Ok, regarding how we control transactions we do it no different from the AS implementation. We basically start the tx before delivery and rollback/commit depending on the outcome. The reason we removed before/afterdelivery is because we shouldn't need to call it as we are starting the tx before the delivery. The issue here is that the TCCL does not get set, looking at the AS code it looks like when the TraditionalXATransactionDemarcationStrategy is used, i.e. https://jira.jboss.org/jira/browse/JBAS-7084 the same problem will occur. Jesper, you should check this. I can change the code back to option B and call before/afterdelivery to fix this but this introduces an extra overhead but its no biggie. The question i was asking is 'is this a bug' and if so, is there a jira and is it due to be fixed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255489#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...