[
https://jira.jboss.org/jira/browse/JBTM-359?page=com.atlassian.jira.plugi...
]
Jonathan Halliday commented on JBTM-359:
----------------------------------------
Having the bridge manage a set of Synchronizations itself seems like duplication of
effort, given that the JTA already has code for that. Better to change the subordinate tx
API exposed by the JTA so that instead of being prepare (with implicit beforeCompletion) +
commit/rollback (with implicit afterCompletion) it exposes before+after as distinct
methods which the bridge can then call from its impl of the XTS VolatileParticipant
methods. That means postponing this one until the API changes in the JTA (JBTM-560) are
done.
Transaction Bridging can timeout b ecause it bundles phase zero work
into prepare
---------------------------------------------------------------------------------
Key: JBTM-359
URL:
https://jira.jboss.org/jira/browse/JBTM-359
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.3.0.GA
Reporter: Andrew Dinn
Assignee: Jonathan Halliday
Fix For: 4.8.0
Bridged (from XTS to JTA) transaction synchronizations currently get executed at prepare
time which can cause very long delays. This may cause the transaction coordinator to
timeout the prepare or cause another participant to timeout. It would be better if the JTA
brdge manager intercepted add synch requests and registered its own phase zero
synchronization to run them.
--
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