Something about this still just doesn't seem right. I am attempting to get with the JBossTS team to discuss what, if anything, we should be doing differently. I am not sure how catching, logging (basically masking) the underlying XA exception is going to help matters. While the JcaXAResourceWrapper could do some trickery to make this problem 'go away' I am not sure this is the right approach. In the tests we are simply reporting what could very well be a real XA exception. If this is causing an IllegalStateException in JBossTS, I would really like to know what and what the *right* way to to fix this is. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008641#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...