Gavin, Your last comment was helpful... anonymous wrote : | I guess this makes sense ... in an MDB, the transaction is committed *after* the Seam contexts have been destroyed. This is not the same lifecycle as in a web request. I added a @TransactionAttribute to my SLSB and that fixed the problem. | @Stateless | @Name("provisionSuccess") | @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) | public class ProvisionSuccessBean implements ProvisionSuccess { | | .... | | } | forcing a separate new transaction to be created for this SLSB, suspending the outer transaction associated with the MDB. So maybe you don't need a JIRA issue for this? rather, documentation should be expanded to explain how to do this? Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013168#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...