And do you get XAER_OUTSIDE for the following change?
| final Connection connection = xaConnection.getConnection(); | connection.setAutoCommit(false); | What about? | final Connection connection = xaConnection.getConnection(); | connection.setAutoCommit(false); | connection.setAutoCommit(true); | If so, like I said before <no-tx-seperate-pools/> will fix it Except for the fact that you are getting the statement before enlisting the XAResource, this is exactly the code that JBoss is executing. Move the XAResource.start() to before the createStatement() to check it exactly, I doubt it will make a difference? For anything further, you need to provide logs, see the post at the top of forum. You still need to ask IBM what the XAER_OUTSIDE means exactly, you can't expect us to keep guessing test code that might reproduce. There aren't enough hours in the day. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009562#4009562 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009562 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
