[
http://jira.jboss.com/jira/browse/JBTM-289?page=comments#action_12398690 ]
Jonathan Halliday commented on JBTM-289:
----------------------------------------
Added similar changes to the JTS implementation, so both it and the local JTA are not JTA
1.1 compliant and use storage on the tx object rather than synchronizations for the locks.
trunk r18374
remove use of Synchronizations for lock storage in jboss integration
--------------------------------------------------------------------
Key: JBTM-289
URL:
http://jira.jboss.com/jira/browse/JBTM-289
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.3.SP5
Reporter: Jonathan Halliday
Assigned To: Jonathan Halliday
Fix For: 4.4, 4.2.3.SP7
JBossAS needs to be able to lock transactions regardless of their state. Since the
current integration implementation uses Synchronizations to store lock state, locking is
possible only during transactions lifecycle phases where Synchronization registration is
permitted. Relax this by changing the integration so that locks are stored using the
general object storage mechanism added to TransactionImple to support JTA 1.1.
--
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