[JBoss JIRA] Created: (JBCACHE-956) Use LockParentForChildInsertRemove flag to control Optimistic node versioning
4:12 p.m.
Use LockParentForChildInsertRemove flag to control Optimistic node versioning
-----------------------------------------------------------------------------
Key: JBCACHE-956
URL: http://jira.jboss.com/jira/browse/JBCACHE-956
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
See JBCACHE-955 for background on locking issues related to inserting and removing child
nodes.
This JIRA is to look into using JBCACHE-955's LockParentForChildInsertRemove flag to
control whether the insertion or removal of a child node affects a workspace node's
data version.
--
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
4:16 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-956) Use LockParentForChildInsertRemove flag to control Optimistic node versioning
[ http://jira.jboss.com/jira/browse/JBCACHE-956?page=comments#action_12351848 ]
Brian Stansberry commented on JBCACHE-956:
------------------------------------------
Manik, we discussed my adding docs for this behavior to LockParentForChildInsertRemove.
Can you do this as part of this JIRA, since it might be done later than JBCACHE-955. I
don't want to doc an unimplemented feature.
Use LockParentForChildInsertRemove flag to control Optimistic node
versioning
-----------------------------------------------------------------------------
Key: JBCACHE-956
URL: http://jira.jboss.com/jira/browse/JBCACHE-956
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Manik Surtani
See JBCACHE-955 for background on locking issues related to inserting and removing child
nodes.
This JIRA is to look into using JBCACHE-955's LockParentForChildInsertRemove flag to
control whether the insertion or removal of a child node affects a workspace node's
data version.
--
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
4:24 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-956) Use LockParentForChildInsertRemove flag to control Optimistic node versioning
[ http://jira.jboss.com/jira/browse/JBCACHE-956?page=all ]
Manik Surtani updated JBCACHE-956:
----------------------------------
Fix Version/s: 2.0.0.BETA1
2.0.0.GA
1.4.1.SP1
Affects Version/s: 1.4.1.GA
Use LockParentForChildInsertRemove flag to control Optimistic node
versioning
-----------------------------------------------------------------------------
Key: JBCACHE-956
URL: http://jira.jboss.com/jira/browse/JBCACHE-956
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.GA
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 1.4.1.SP1, 2.0.0.BETA1, 2.0.0.GA
See JBCACHE-955 for background on locking issues related to inserting and removing child
nodes.
This JIRA is to look into using JBCACHE-955's LockParentForChildInsertRemove flag to
control whether the insertion or removal of a child node affects a workspace node's
data version.
--
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
2:16 p.m.
New subject: [JBoss JIRA] Closed: (JBCACHE-956) Use LockParentForChildInsertRemove flag to control Optimistic node versioning
[ http://jira.jboss.com/jira/browse/JBCACHE-956?page=all ]
Manik Surtani closed JBCACHE-956.
---------------------------------
Fix Version/s: (was: 2.0.0.GA)
(was: 2.0.0.BETA1)
Resolution: Won't Fix
Use LockParentForChildInsertRemove flag to control Optimistic node
versioning
-----------------------------------------------------------------------------
Key: JBCACHE-956
URL: http://jira.jboss.com/jira/browse/JBCACHE-956
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.GA
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 1.4.1.SP1
See JBCACHE-955 for background on locking issues related to inserting and removing child
nodes.
This JIRA is to look into using JBCACHE-955's LockParentForChildInsertRemove flag to
control whether the insertion or removal of a child node affects a workspace node's
data version.
--
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
2:16 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-956) Use LockParentForChildInsertRemove flag to control Optimistic node versioning
[ http://jira.jboss.com/jira/browse/JBCACHE-956?page=comments#action_12351941 ]
Manik Surtani commented on JBCACHE-956:
---------------------------------------
This actually does not work for optimistic locking and here's why.
Whenever a node is added, the following happens:
1) Parent read into TX Workspace (call this parentW)
2) New node created in workspace
3) New node added to parentW's child map
4) At commit, parentW's child map is used to overwrite parent's child map
Because of step 4, there is no way we can support concurrent adds/removes on parent nodes
without implementing a diffing/merging algorithm for child maps. Step 4 has to be an
overwrite since we don't know whether part of the tx also involved removing children
unless we have a merging algo.
I agree that this is pretty crap and we do need something more sophisticated here, but I
don't think it is correct to do in 1.4.1.SP1.
See JBCACHE-961
Use LockParentForChildInsertRemove flag to control Optimistic node
versioning
-----------------------------------------------------------------------------
Key: JBCACHE-956
URL: http://jira.jboss.com/jira/browse/JBCACHE-956
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.GA
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 1.4.1.SP1
See JBCACHE-955 for background on locking issues related to inserting and removing child
nodes.
This JIRA is to look into using JBCACHE-955's LockParentForChildInsertRemove flag to
control whether the insertion or removal of a child node affects a workspace node's
data version.
--
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
4:45 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-956) Use LockParentForChildInsertRemove flag to control Optimistic node versioning
[ http://jira.jboss.com/jira/browse/JBCACHE-956?page=comments#action_12351957 ]
Brian Stansberry commented on JBCACHE-956:
------------------------------------------
NP. Glad I didn't doc it. :-)
Use LockParentForChildInsertRemove flag to control Optimistic node
versioning
-----------------------------------------------------------------------------
Key: JBCACHE-956
URL: http://jira.jboss.com/jira/browse/JBCACHE-956
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.GA
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 1.4.1.SP1
See JBCACHE-955 for background on locking issues related to inserting and removing child
nodes.
This JIRA is to look into using JBCACHE-955's LockParentForChildInsertRemove flag to
control whether the insertion or removal of a child node affects a workspace node's
data version.
--
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
12:07 p.m.
New subject: [JBoss JIRA] Reopened: (JBCACHE-956) Use LockParentForChildInsertRemove flag to control Optimistic node versioning
[ http://jira.jboss.com/jira/browse/JBCACHE-956?page=all ]
Manik Surtani reopened JBCACHE-956:
-----------------------------------
reopening
Use LockParentForChildInsertRemove flag to control Optimistic node
versioning
-----------------------------------------------------------------------------
Key: JBCACHE-956
URL: http://jira.jboss.com/jira/browse/JBCACHE-956
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.GA
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.0.0.GA, 2.0.0.BETA2
See JBCACHE-955 for background on locking issues related to inserting and removing child
nodes.
This JIRA is to look into using JBCACHE-955's LockParentForChildInsertRemove flag to
control whether the insertion or removal of a child node affects a workspace node's
data version.
--
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
12:07 p.m.
New subject: [JBoss JIRA] Closed: (JBCACHE-956) Use LockParentForChildInsertRemove flag to control Optimistic node versioning
[ http://jira.jboss.com/jira/browse/JBCACHE-956?page=all ]
Manik Surtani closed JBCACHE-956.
---------------------------------
Fix Version/s: 2.0.0.BETA2
2.0.0.GA
(was: 1.4.1.SP1)
Resolution: Done
Use LockParentForChildInsertRemove flag to control Optimistic node
versioning
-----------------------------------------------------------------------------
Key: JBCACHE-956
URL: http://jira.jboss.com/jira/browse/JBCACHE-956
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.GA
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.0.0.BETA2, 2.0.0.GA
See JBCACHE-955 for background on locking issues related to inserting and removing child
nodes.
This JIRA is to look into using JBCACHE-955's LockParentForChildInsertRemove flag to
control whether the insertion or removal of a child node affects a workspace node's
data version.
--
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
11:36 a.m.
New subject: [JBoss JIRA] Closed: (JBCACHE-956) Use LockParentForChildInsertRemove flag to control Optimistic node versioning
[ http://jira.jboss.com/jira/browse/JBCACHE-956?page=all ]
Manik Surtani closed JBCACHE-956.
---------------------------------
Fix Version/s: 1.4.1.SP3
Resolution: Done
This is fixed in 1.4.1.SP3
Use LockParentForChildInsertRemove flag to control Optimistic node
versioning
-----------------------------------------------------------------------------
Key: JBCACHE-956
URL: http://jira.jboss.com/jira/browse/JBCACHE-956
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.GA
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.0.0.GA, 1.4.1.SP3, 2.0.0.BETA2
See JBCACHE-955 for background on locking issues related to inserting and removing child
nodes.
This JIRA is to look into using JBCACHE-955's LockParentForChildInsertRemove flag to
control whether the insertion or removal of a child node affects a workspace node's
data version.
--
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
11:36 a.m.
New subject: [JBoss JIRA] Reopened: (JBCACHE-956) Use LockParentForChildInsertRemove flag to control Optimistic node versioning
[ http://jira.jboss.com/jira/browse/JBCACHE-956?page=all ]
Manik Surtani reopened JBCACHE-956:
-----------------------------------
Use LockParentForChildInsertRemove flag to control Optimistic node
versioning
-----------------------------------------------------------------------------
Key: JBCACHE-956
URL: http://jira.jboss.com/jira/browse/JBCACHE-956
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.GA
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.0.0.GA, 2.0.0.BETA2, 1.4.1.SP3
See JBCACHE-955 for background on locking issues related to inserting and removing child
nodes.
This JIRA is to look into using JBCACHE-955's LockParentForChildInsertRemove flag to
control whether the insertion or removal of a child node affects a workspace node's
data version.
--
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
7026
days inactive
7104
days old
9 comments
3 participants
participants (3)
-
Brian Stansberry (JIRA) -
Manik Surtani (JIRA) -
Manik Surtani (JIRA)