[JBoss JIRA] (JBTM-2583) Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2583:
--------------------------------
Summary: Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection (was: Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection)
> Use the local ActionStatusService to determine if a transaction containing XAResources is still in-flight before relying on orphan detection
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-2583
> URL: https://issues.jboss.org/browse/JBTM-2583
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Recovery
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.later
>
>
> Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager.
> This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back.
>
> * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely
> * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
- 1
- 0
[JBoss JIRA] (JBTM-2631) UidTest qa test suite (with the journal store) failures
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2631?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2631:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> UidTest qa test suite (with the journal store) failures
> -------------------------------------------------------
>
> Key: JBTM-2631
> URL: https://issues.jboss.org/browse/JBTM-2631
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Testing
> Affects Versions: 5.2.14.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Attachments: testoutput.jacorb.hqstore.tar
>
>
> CI job http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/... failed with various uid test failures:
> {quote}
> txcore Uid_Test011 Fail (0m18.180s)
> txcore Uid_Test011 Fail (0m19.431s)
> txcore Uid_Test012 Fail (0m20.850s)
> txcore Uid_Test004 Fail (0m11.566s)
> txcore Uid_Test005 Fail (0m12.343s)
> txcore Uid_Test006 Fail (0m12.062s)
> txcore Uid_Test007 Fail (0m15.742s)
> txcore Uid_Test008 Fail (0m16.908s)
> txcore Uid_Test009 Fail (0m17.282s)
> txcore_lockrecord LockRecord_Thread_Test036a Fail (8m12.773s)
> txcore_lockrecord LockRecord_Thread_Test036b Fail (8m10.265s)
> txcore_lockrecord LockRecord_Thread_Test048a Fail (8m11.115s)
> txcore_lockrecord LockRecord_Thread_Test048b Fail (8m7.376s)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
- 1
- 0