I can't control the usage of setRollbackOnly(), it is exposed in JAIN SLEE applications API. For now I think I will go for a solution where an interceptor makes any cache update fail if no tx is present or it is not in active or rollback state, and keep trapping the set rollback operation. Another doubt, it is safe to use the same node instance in multiple transactions? I'm not doing that now but if it is safe I would consider for some nodes that are bound to factory type objects which are singleton and are made on server start. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204326#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...