[JBoss JIRA] (JBTM-1249) XA recovery Failed on Oracle (pad-xid=true not propagated to the XARecoveryModule)
4:34 a.m.
Michel PRUNET created JBTM-1249:
-----------------------------------
Summary: XA recovery Failed on Oracle (pad-xid=true not propagated to the
XARecoveryModule)
Key: JBTM-1249
URL: https://issues.jboss.org/browse/JBTM-1249
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Application Server Integration, JCA, JTS
Affects Versions: 4.16.2
Environment: JBoss AS 7.1.1 Final, Windows, Oracle
Reporter: Michel PRUNET
Assignee: Tom Jenkinson
The XARecoveryManager is unable to recover an Oracle Prepared Transaction.
The reason:
Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource).
When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is
not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids
are padded (retrieved from oracle). When the method execute xids.remove(xid), it never
found the xid. The transaction is never recovered.
In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or
bqual_length), the transaction will be recovered successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:39 a.m.
[
https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin....
]
Jonathan Halliday commented on JBTM-1249:
-----------------------------------------
I last looked at this some years ago and was unable to reproduce it. We'll need the
version of oracle server and driver, plus ideally the content of the objectstore and the
data from DBA_2PC_PENDING. It's likely attributable to something in the
XidImple.generateHash usage. Since our internal XID.data arrays are always zero padded
anyhow, the hash calculation should probably just ignore the length params and always
operate over the full array.
XA recovery Failed on Oracle (pad-xid=true not propagated to the
XARecoveryModule)
----------------------------------------------------------------------------------
Key: JBTM-1249
URL: https://issues.jboss.org/browse/JBTM-1249
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration, JCA, JTS
Affects Versions: 4.16.2
Environment: JBoss AS 7.1.1 Final, Windows, Oracle
Reporter: Michel PRUNET
Assignee: Tom Jenkinson
Labels: jboss, jts, recovery, xa
The XARecoveryManager is unable to recover an Oracle Prepared Transaction.
The reason:
Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource).
When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is
not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids
are padded (retrieved from oracle). When the method execute xids.remove(xid), it never
found the xid. The transaction is never recovered.
In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or
bqual_length), the transaction will be recovered successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:48 p.m.
[
https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin....
]
Michel PRUNET commented on JBTM-1249:
-------------------------------------
Hello jonathan,
I investigate on this, I'll try to give you maximum information and possibly a
reproductible test case.
Thank you for your reactivity
Best regards
Michel
XA recovery Failed on Oracle (pad-xid=true not propagated to the
XARecoveryModule)
----------------------------------------------------------------------------------
Key: JBTM-1249
URL: https://issues.jboss.org/browse/JBTM-1249
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration, JCA, JTS
Affects Versions: 4.16.2
Environment: JBoss AS 7.1.1 Final, Windows, Oracle
Reporter: Michel PRUNET
Assignee: Tom Jenkinson
Labels: jboss, jts, recovery, xa
The XARecoveryManager is unable to recover an Oracle Prepared Transaction.
The reason:
Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource).
When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is
not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids
are padded (retrieved from oracle). When the method execute xids.remove(xid), it never
found the xid. The transaction is never recovered.
In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or
bqual_length), the transaction will be recovered successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:53 a.m.
[
https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin....
]
Michel PRUNET updated JBTM-1249:
--------------------------------
Attachment: TestEJB.zip
Hello Jonathan,
Everything is inside the TestEJB.zip file.
Have a look into README.txt
Best Regards
Michel
XA recovery Failed on Oracle (pad-xid=true not propagated to the
XARecoveryModule)
----------------------------------------------------------------------------------
Key: JBTM-1249
URL: https://issues.jboss.org/browse/JBTM-1249
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration, JCA, JTS
Affects Versions: 4.16.2
Environment: JBoss AS 7.1.1 Final, Windows, Oracle
Reporter: Michel PRUNET
Assignee: Tom Jenkinson
Labels: jboss, jts, recovery, xa
Attachments: TestEJB.zip
The XARecoveryManager is unable to recover an Oracle Prepared Transaction.
The reason:
Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource).
When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is
not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids
are padded (retrieved from oracle). When the method execute xids.remove(xid), it never
found the xid. The transaction is never recovered.
In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or
bqual_length), the transaction will be recovered successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:57 a.m.
[
https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin....
]
Michel PRUNET commented on JBTM-1249:
-------------------------------------
A simple workaround is to set pad-xid to false.
Oracle 11g doesn't need it anymore.
Michel
XA recovery Failed on Oracle (pad-xid=true not propagated to the
XARecoveryModule)
----------------------------------------------------------------------------------
Key: JBTM-1249
URL: https://issues.jboss.org/browse/JBTM-1249
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration, JCA, JTS
Affects Versions: 4.16.2
Environment: JBoss AS 7.1.1 Final, Windows, Oracle
Reporter: Michel PRUNET
Assignee: Tom Jenkinson
Labels: jboss, jts, recovery, xa
Attachments: TestEJB.zip
The XARecoveryManager is unable to recover an Oracle Prepared Transaction.
The reason:
Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource).
When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is
not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids
are padded (retrieved from oracle). When the method execute xids.remove(xid), it never
found the xid. The transaction is never recovered.
In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or
bqual_length), the transaction will be recovered successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:56 p.m.
[
https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1249:
--------------------------------
Fix Version/s: 4.17.4
5.0.0.M2
XA recovery Failed on Oracle (pad-xid=true not propagated to the
XARecoveryModule)
----------------------------------------------------------------------------------
Key: JBTM-1249
URL: https://issues.jboss.org/browse/JBTM-1249
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration, JCA, JTS
Affects Versions: 4.16.2
Environment: JBoss AS 7.1.1 Final, Windows, Oracle
Reporter: Michel PRUNET
Assignee: Tom Jenkinson
Labels: jboss, jts, recovery, xa
Fix For: 4.17.4, 5.0.0.M2
Attachments: TestEJB.zip
The XARecoveryManager is unable to recover an Oracle Prepared Transaction.
The reason:
Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource).
When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is
not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids
are padded (retrieved from oracle). When the method execute xids.remove(xid), it never
found the xid. The transaction is never recovered.
In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or
bqual_length), the transaction will be recovered successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:44 a.m.
[
https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1249:
-------------------------------------
Do you agree that this can be resolved by a documentation fix to ensure that Oracle 11g
and above datasources should not be configured with pad-xid set to true?
XA recovery Failed on Oracle (pad-xid=true not propagated to the
XARecoveryModule)
----------------------------------------------------------------------------------
Key: JBTM-1249
URL: https://issues.jboss.org/browse/JBTM-1249
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration, JCA, JTS
Affects Versions: 4.16.2
Environment: JBoss AS 7.1.1 Final, Windows, Oracle
Reporter: Michel PRUNET
Assignee: Tom Jenkinson
Labels: jboss, jts, recovery, xa
Fix For: 4.17.4, 5.0.0.M2
Attachments: TestEJB.zip
The XARecoveryManager is unable to recover an Oracle Prepared Transaction.
The reason:
Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource).
When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is
not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids
are padded (retrieved from oracle). When the method execute xids.remove(xid), it never
found the xid. The transaction is never recovered.
In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or
bqual_length), the transaction will be recovered successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:38 a.m.
[
https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin....
]
Michel PRUNET commented on JBTM-1249:
-------------------------------------
I agree with that.
XA recovery Failed on Oracle (pad-xid=true not propagated to the
XARecoveryModule)
----------------------------------------------------------------------------------
Key: JBTM-1249
URL: https://issues.jboss.org/browse/JBTM-1249
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration, JCA, JTS
Affects Versions: 4.16.2
Environment: JBoss AS 7.1.1 Final, Windows, Oracle
Reporter: Michel PRUNET
Assignee: Tom Jenkinson
Labels: jboss, jts, recovery, xa
Fix For: 4.17.4, 5.0.0.M2
Attachments: TestEJB.zip
The XARecoveryManager is unable to recover an Oracle Prepared Transaction.
The reason:
Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource).
When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is
not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids
are padded (retrieved from oracle). When the method execute xids.remove(xid), it never
found the xid. The transaction is never recovered.
In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or
bqual_length), the transaction will be recovered successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:06 a.m.
[
https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1249:
--------------------------------
Component/s: Documentation
XA recovery Failed on Oracle (pad-xid=true not propagated to the
XARecoveryModule)
----------------------------------------------------------------------------------
Key: JBTM-1249
URL: https://issues.jboss.org/browse/JBTM-1249
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration, Documentation, JCA, JTS
Affects Versions: 4.16.2
Environment: JBoss AS 7.1.1 Final, Windows, Oracle
Reporter: Michel PRUNET
Assignee: Tom Jenkinson
Labels: jboss, jts, recovery, xa
Fix For: 4.17.4, 5.0.0.M2
Attachments: TestEJB.zip
The XARecoveryManager is unable to recover an Oracle Prepared Transaction.
The reason:
Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource).
When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is
not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids
are padded (retrieved from oracle). When the method execute xids.remove(xid), it never
found the xid. The transaction is never recovered.
In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or
bqual_length), the transaction will be recovered successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:06 a.m.
[
https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1249:
-------------------------------------
Thanks Michel, I will add some comments into our docs.
XA recovery Failed on Oracle (pad-xid=true not propagated to the
XARecoveryModule)
----------------------------------------------------------------------------------
Key: JBTM-1249
URL: https://issues.jboss.org/browse/JBTM-1249
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration, Documentation, JCA, JTS
Affects Versions: 4.16.2
Environment: JBoss AS 7.1.1 Final, Windows, Oracle
Reporter: Michel PRUNET
Assignee: Tom Jenkinson
Labels: jboss, jts, recovery, xa
Fix For: 4.17.4, 5.0.0.M2
Attachments: TestEJB.zip
The XARecoveryManager is unable to recover an Oracle Prepared Transaction.
The reason:
Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource).
When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is
not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids
are padded (retrieved from oracle). When the method execute xids.remove(xid), it never
found the xid. The transaction is never recovered.
In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or
bqual_length), the transaction will be recovered successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:08 a.m.
[
https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1249:
--------------------------------
Parent: JBTM-1184
Issue Type: Sub-task (was: Bug)
XA recovery Failed on Oracle (pad-xid=true not propagated to the
XARecoveryModule)
----------------------------------------------------------------------------------
Key: JBTM-1249
URL: https://issues.jboss.org/browse/JBTM-1249
Project: JBoss Transaction Manager
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Application Server Integration, Documentation, JCA, JTS
Affects Versions: 4.16.2
Environment: JBoss AS 7.1.1 Final, Windows, Oracle
Reporter: Michel PRUNET
Assignee: Tom Jenkinson
Labels: jboss, jts, recovery, xa
Fix For: 4.17.4, 5.0.0.M2
Attachments: TestEJB.zip
The XARecoveryManager is unable to recover an Oracle Prepared Transaction.
The reason:
Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource).
When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is
not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids
are padded (retrieved from oracle). When the method execute xids.remove(xid), it never
found the xid. The transaction is never recovered.
In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or
bqual_length), the transaction will be recovered successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:02 p.m.
[
https://issues.jboss.org/browse/JBTM-1249?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1249:
--------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M2)
XA recovery Failed on Oracle (pad-xid=true not propagated to the
XARecoveryModule)
----------------------------------------------------------------------------------
Key: JBTM-1249
URL: https://issues.jboss.org/browse/JBTM-1249
Project: JBoss Transaction Manager
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Application Server Integration, Documentation, JCA, JTS
Affects Versions: 4.16.2
Environment: JBoss AS 7.1.1 Final, Windows, Oracle
Reporter: Michel PRUNET
Assignee: Tom Jenkinson
Labels: jboss, jts, recovery, xa
Fix For: 4.17.4, 5.0.0.Final
Attachments: TestEJB.zip
The XARecoveryManager is unable to recover an Oracle Prepared Transaction.
The reason:
Oracle needs the Xid to be padded (pad-xid set to true in xa-datasource).
When the method XARecoveryModule.getNewXAResource(Xid xid) is called. The value of xid is
not padded (retrieved from the tx-object-store). The XID contained in the RecoveryXids
are padded (retrieved from oracle). When the method execute xids.remove(xid), it never
found the xid. The transaction is never recovered.
In a debug session, if you pad the xid in that method (change the xid.gtrud_length and or
bqual_length), the transaction will be recovered successfully.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4159
days inactive
4241
days old
jbossts-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Jonathan Halliday (JIRA) -
Michel PRUNET (JIRA)
-
Tom Jenkinson (JIRA)