I had the same problem which on my side was caused by accessing 2 different data-sources within the same transaction (XA transaction on Oracle database). E.g. Method X is calling method Y which does an database A insert and calls method Z which does a database B update. The solution was to annotate method Y and method Z with: @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW) Hope this helps. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261262#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...