[jbossts-issues] [JBoss JIRA] Updated: (JBTM-289) remove use of Synchronizations for lock storage in jboss integration

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Wed Oct 3 10:46:03 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBTM-289?page=all ]

Jonathan Halliday updated JBTM-289:

    Fix Version/s: 4.2.3.SP7
                       (was: 4.2.3.SP6)

> 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


More information about the jbossts-issues mailing list