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

[Jonathan Halliday (Assigned) (JIRA)]

     [ https://issues.jboss.org/browse/JBAS-8698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Halliday reassigned JBAS-8698:
---------------------------------------

    Assignee:     (was: Jonathan Halliday)

    
> Datasource XAExceptions leads to corrupt Transaction Context on thread
> ----------------------------------------------------------------------
>
>                 Key: JBAS-8698
>                 URL: https://issues.jboss.org/browse/JBAS-8698
>             Project: Application Server 3, 4, 5 and 6
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: ClassLoading, Remoting, Transaction Manager Integration (Arjuna)
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.1.0.GA, 6.0.0.CR1
>            Reporter: Anders Welen
>             Fix For: No Release
>
>         Attachments: JBoss_5.1_JBAS-8698.patch, mysql-ds.xml, 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)
> ...
> ...
> ...
> From what I can see the "MysqlXAException" (implements XAException)  will not be caught in "com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.java". (Can it be some kind of classloading problem?) As the result the thread will not be cleaned of transaction information and "broken" when reused. 
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira