]
Jonathan Halliday updated JBTM-541:
-----------------------------------
Fix Version/s: 4.8.0
(was: 4.7.0)
Postponing pending provision of a test case.
Enhance support for MySQL XA connections
----------------------------------------
Key: JBTM-541
URL:
https://jira.jboss.org/jira/browse/JBTM-541
Project: JBoss Transaction Manager
Issue Type: Patch
Security Level: Public(Everyone can see)
Components: JTA
Affects Versions: 4.6.1
Reporter: mohankishore
Assignee: Jonathan Halliday
Fix For: 4.8.0
Attachments: ConnectionImple.patch, TransactionImple.patch
As generally accepted, the MySQL support for XA is somewhat broken.
If you do the following:
- begin a transaction
- get an XAConnection from MySQL,
- get a connection from the XAC
- do some operations,
- close the connection
- get another connection from XAC
- try to do some operations -> MYSQL throws an exception stating that it does not
support a XA START RESUME
But, this leads to certain undesirable behavior inside the JBOSS JTA codebase. It is
resulting in not calling XAC.close(). We are using a custom pool for limiting the number
of XAConnections we create - which gets maxed out because of this. Am attaching a patch
for ConnectionImple that fixes the logic in the close() method. Also has a couple of jdk6
methods that allow the client to access the underlying native conneciton..
Am also adding a patch for the TransactionImple - which ensures that we call
XAResource.rollback() - cleaning up the XAC for subsequent reuse.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: