Factor XAResourceRecovery creation out of RecoveryModule
--------------------------------------------------------
Key: JBTM-224
URL: http://jira.jboss.com/jira/browse/JBTM-224
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JTA Implementation, JTS Implementation
Affects Versions: 4.2.3.SP4
Reporter: Mark Little
Assigned To: Mark Little
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Potential race condition in top-down/bottom-up recovery with XA_RETRY
---------------------------------------------------------------------
Key: JBTM-225
URL: http://jira.jboss.com/jira/browse/JBTM-225
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JTA Implementation, JTS Implementation
Affects Versions: 4.2.3.SP4
Reporter: Mark Little
Assigned To: Mark Little
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
LRCO update
-----------
Key: JBTM-499
URL: https://jira.jboss.org/jira/browse/JBTM-499
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Transaction Core
Affects Versions: 4.5
Reporter: Mark Little
Assignee: Mark Little
Work to pass intentions list processing to local db transaction done in scope of partner effort but not checked in.
--
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
Support original LRCO implementation
------------------------------------
Key: JBTM-413
URL: https://jira.jboss.org/jira/browse/JBTM-413
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Transaction Core
Affects Versions: 4.4.0.GA
Reporter: Mark Little
Assignee: Mark Little
Fix For: 4.6
--
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
Check lifetime of transactions during recovery
----------------------------------------------
Key: JBTM-368
URL: http://jira.jboss.com/jira/browse/JBTM-368
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Recovery
Reporter: Mark Little
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Compile list of refactor/consolidation options with existing code.
------------------------------------------------------------------
Key: JBTM-398
URL: https://jira.jboss.org/jira/browse/JBTM-398
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JTA Implementation, JTS Implementation, Transaction Core, WS-T Implementation
Reporter: Mark Little
Assignee: Mark Little
Fix For: 4.6
--
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
Reduce synchronization boundaries on LockManager.setlock
--------------------------------------------------------
Key: JBTM-618
URL: https://jira.jboss.org/jira/browse/JBTM-618
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Transaction Core
Affects Versions: 4.2.3.CP06
Reporter: Mark Little
Assignee: Mark Little
Fix For: 5.0.0
Currently too coarse grained.
--
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
Periodic commit retry
---------------------
Key: JBTM-528
URL: https://jira.jboss.org/jira/browse/JBTM-528
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JTA
Reporter: Mark Little
Assignee: Mark Little
Fix For: 5.0.0
XA_RETRY on commit ...
/*
* Could do timeout retry here, but that could cause other resources in the list to go down the
* heuristic path (some are far too keen to do this). Fail and let recovery retry. Meanwhile
* the coordinator will continue to commit the other resources immediately.
*/
--
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
Check conformance and compatibility of two JTA implementations
--------------------------------------------------------------
Key: JBTM-251
URL: http://jira.jboss.com/jira/browse/JBTM-251
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.3.SP5
Reporter: Mark Little
Assigned To: Andrew Dinn
Make sure that both of our JTA implementations behave as similarly as possible from an interface perspective. For example, that timeouts are handled the same. Some differences are bound to be visible because the two implementations have different capabilities. But ignoring those, we need to be as consistent as possible.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
crash recovery testing with AS integration
------------------------------------------
Key: JBTM-336
URL: http://jira.jboss.com/jira/browse/JBTM-336
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.3.0.BETA2
Reporter: Jonathan Halliday
Fix For: 4.4
Current testing of JBossTS is standalone. The JBossAS integration code does not get exercised. This a particularly a problem for specialized crash recovery modules that are used only when running integrated with AS. Work with the AS team to figure out how best to do crash recovery testing for JBossAS.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira