It's a common practice to do: | try | { | } | catch (Exception e) | { | log.warn (e.getMessage(), e); | transaction.setRollbackOnly(); | } | Maybe some other exception happened, and set the transaction in abort mode. Maybe you have a case where you are setting the transaction to rollback and not logging the exception. (Well.. maybe something on AS code is doing the similar behavior (not logging the exception). I don't think that's the case but it's not impossible). If you have how to reproduce this, maybe you should look for more exceptions, debug it, add more logs.. don't know. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169649#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...