[jbossts-issues] [JBoss JIRA] (JBTM-1737) Set different sub-root for persistent lock store or we delete persistent object states

Mark Little (JIRA) jira-events at lists.jboss.org
Mon Jun 3 11:48:54 EDT 2013


     [ https://issues.jboss.org/browse/JBTM-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Little resolved JBTM-1737.
-------------------------------

    Resolution: Done

    
> Set different sub-root for persistent lock store or we delete persistent object states
> --------------------------------------------------------------------------------------
>
>                 Key: JBTM-1737
>                 URL: https://issues.jboss.org/browse/JBTM-1737
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Core
>    Affects Versions: 5.0.0.M3
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>            Priority: Critical
>             Fix For: 5.0.0.M4
>
>
> BasicPersistentLockStore saves lock states in the object store so they can be shared between address spaces. In the past this relied on creating its own object store with a different root. With the refactoring of object stores that occurred a couple of years ago, this got overlooked and was using the exact same object store root, with the exact same state Uid as related TXOJ instances. This meant that lock states could overwrite object states and deleting lock states could delete object states.
> Use a sub-root in the object store for uniqueness.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbossts-issues mailing list