Issue created at https://jira.jboss.org/jira/browse/JBCACHE-1468 I'm currenlty using a workaround which consists in trapping the setRollbackOnly(), saving a flag that set rollback in transaction local data, and don't do that in the transaction manager, of course getRollabckOnly considers the flag for result, and commit will rollback if the flag is set, but I'm not sure that due to not setting it in the tx manager something bad can come in its resources. By the way, is there a way to make JBoss Cache fail if no transaction exists other than add an interceptor? -- Eduardo View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204113#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...