[JBoss JIRA] (JBTM-1249) XA recovery Failed on Oracle (pad-xid=true not propagated to the XARecoveryModule)
by Michel PRUNET (JIRA)
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
12 years
[JBoss JIRA] (JBTM-1116) Document properties
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-1116:
-----------------------------------
Summary: Document properties
Key: JBTM-1116
URL: https://issues.jboss.org/browse/JBTM-1116
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Documentation
Reporter: Tom Jenkinson
Assignee: Tom Jenkinson
In the pre-Bean days of setting properties, we had all of the TS properties called out in a properties.xml file. In that file there were copious comments to say what the property was for and whether it should be changed. We also documented these properties in the docs. It seems from some investigation that Mike and I have done today that the migration away from the properties file to using MBeans has removed those comments and the docs for the properties. Sometimes the comments do appear in the code.
If you go back to before everything got turned everything into a Bean (probably 4.6.1 GA) then look in the etc directories.
--
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
12 years
[JBoss JIRA] (JBTM-1106) BA client-side support
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1106:
-----------------------------------
Summary: BA client-side support
Key: JBTM-1106
URL: https://issues.jboss.org/browse/JBTM-1106
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Priority: Minor
Fix For: 5.0.0.Final
See the "Policy Assertions" section of the WS-BA and WS-AT specification for what this should implement. Ideally this feature would be turned on/off via an annotation, however we should take a look to see if WS-Policy mandates a particular method.
--
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
12 years