June 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1738) Allow sharing of states between address spaces for STM applications and add some tests.

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1738?page=com.atlassian.jira.plugin.... ] Mark Little resolved JBTM-1738. ------------------------------- Resolution: Done > Allow sharing of states between address spaces for STM applications and add some tests. > --------------------------------------------------------------------------------------- > > Key: JBTM-1738 > URL: https://issues.jboss.org/browse/JBTM-1738 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > Fix For: 5.0.0.M4 > > > Support ObjectModel.MULTIPLE in the containers. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1738) Allow sharing of states between address spaces for STM applications and add some tests.

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1738?page=com.atlassian.jira.plugin.... ] Mark Little updated JBTM-1738: ------------------------------ Description: Support ObjectModel.MULTIPLE in the containers. > Allow sharing of states between address spaces for STM applications and add some tests. > --------------------------------------------------------------------------------------- > > Key: JBTM-1738 > URL: https://issues.jboss.org/browse/JBTM-1738 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > Fix For: 5.0.0.M4 > > > Support ObjectModel.MULTIPLE in the containers. -- 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

10 years, 11 months

1
0
0 / 0

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

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1737?page=com.atlassian.jira.plugin.... ] Mark Little updated JBTM-1737: ------------------------------ Assignee: Mark Little (was: Tom Jenkinson) > 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: Mark Little > 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1738) Allow sharing of states between address spaces for STM applications and add some tests.

by Mark Little (JIRA)

Mark Little created JBTM-1738: --------------------------------- Summary: Allow sharing of states between address spaces for STM applications and add some tests. Key: JBTM-1738 URL: https://issues.jboss.org/browse/JBTM-1738 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: STM Affects Versions: 5.0.0.M3 Reporter: Mark Little Assignee: Mark Little Fix For: 5.0.0.M4 -- 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

10 years, 11 months

1
0
0 / 0

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

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1737?page=com.atlassian.jira.plugin.... ] Mark Little closed JBTM-1737. ----------------------------- > 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: Mark Little > 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

10 years, 11 months

1
0
0 / 0

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

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1737?page=com.atlassian.jira.plugin.... ] 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

10 years, 11 months

1
0
0 / 0

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

by Mark Little (JIRA)

Mark Little created JBTM-1737: --------------------------------- Summary: 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1736) NPE in LockManager/LockConflictManager during setlock

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1736?page=com.atlassian.jira.plugin.... ] Mark Little resolved JBTM-1736. ------------------------------- Resolution: Done > NPE in LockManager/LockConflictManager during setlock > ----------------------------------------------------- > > Key: JBTM-1736 > URL: https://issues.jboss.org/browse/JBTM-1736 > 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: Mark Little > Fix For: 5.0.0.M4 > > > ReentrantLock was not always set when passed through the LockConflictManager. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1736) NPE in LockManager/LockConflictManager during setlock

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1736?page=com.atlassian.jira.plugin.... ] Mark Little closed JBTM-1736. ----------------------------- > NPE in LockManager/LockConflictManager during setlock > ----------------------------------------------------- > > Key: JBTM-1736 > URL: https://issues.jboss.org/browse/JBTM-1736 > 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: Mark Little > Fix For: 5.0.0.M4 > > > ReentrantLock was not always set when passed through the LockConflictManager. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1736) NPE in LockManager/LockConflictManager during setlock

by Mark Little (JIRA)

Mark Little created JBTM-1736: --------------------------------- Summary: NPE in LockManager/LockConflictManager during setlock Key: JBTM-1736 URL: https://issues.jboss.org/browse/JBTM-1736 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: Mark Little Fix For: 5.0.0.M4 ReentrantLock was not always set when passed through the LockConflictManager. -- 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

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2013