[
https://jira.jboss.org/jira/browse/JBTM-619?page=com.atlassian.jira.plugi...
]
Wade Poziombka commented on JBTM-619:
-------------------------------------
I have confirmed that this issue only exists when the two connections are to the same
database instance. Two separate Oracle instances do not have this issue.
Cannot enlist two Oracle XAConnection resources in one transaction
------------------------------------------------------------------
Key: JBTM-619
URL:
https://jira.jboss.org/jira/browse/JBTM-619
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTA
Affects Versions: 4.7.0
Environment: Windows and Linux.
Reporter: Wade Poziombka
An attempt to enlist two Oracle connections causes the second enlistResource to fail with
an exception similar to:
oracle.jdbc.xa.OracleXAException
at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:938)
at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:244)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:902)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:513)
Note the line number changes a bit depending on version of Oracle JDBC etc. However, the
affect is always the same.
There are others who noted this problem on the forum with no resolution or reply (except
my own concurring with the observation).
In particular two connections to same server using different user id's and passwords.
I will test whether two completely separate oracle instances have this issue and update
the bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira