[
https://issues.jboss.org/browse/JBTM-2165?page=com.atlassian.jira.plugin....
]
Michael Musgrove updated JBTM-2165:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request:
https://github.com/jbosstm/narayana/pull/658,
https://github.com/jbosstm/narayana/pull/659
A normal beforeCompletion synchronisation (aka session synch) is allowed to enlist a CMR
resource into a transaction which in turn will register its own synch. The latter must be
ordered after any synchs that have already ran or are already running.
The fix is to register CMR synchs as interposed (see
javax.transaction.TransactionSynchronizationRegistry#registerInterposedSynchronization)
which are guaranteed to run after all normal session synchs have been called.
CMR synchronisations should be interposed
-----------------------------------------
Key: JBTM-2165
URL:
https://issues.jboss.org/browse/JBTM-2165
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTA
Affects Versions: 4.17.19, 5.0.1
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 4.17.20, 5.0.2
A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it
is possible for another synchronization to enlist a CMR resource the CMR synch must be
ordered after non interposed synchronizations.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)