[jboss-jira] [JBoss JIRA] Created: (JBAS-8698) Datasource XAExceptions leads to corrupt Transaction Context on thread

Datasource XAExceptions leads to corrupt Transaction Context on thread ---------------------------------------------------------------------- Key: JBAS-8698 URL: https://jira.jboss.org/browse/JBAS-8698 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading, Remoting, Transaction Manager Integration (Arjuna) Affects Versions: 6.0.0.CR1, JBossAS-5.1.0.GA, JBossAS-4.2.1.GA Reporter: Anders Welen Assignee: Scott Stark Attachments: TestCase3850.tar When MySQL throws a "com.mysql.jdbc.jdbc2.optional.MysqlXAException" when called from a remote client the server thread doesn't seem to be cleaned up of transaction context data. All calls that reusing the thread will fail with the following exception: org.jboss.util.NestedSQLException: Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000002:e137:4cf78939:68 status: ActionStatus.COMMITTING >; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000002:e137:4cf78939:68 status: ActionStatus.COMMITTING >) at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95) at se.redpill.TestCase3850Bean.runTest(TestCase3850Bean.java:22) ... ... ... This seems only to occur for remote clients (If the client calls within the JVM it seems to work) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira