January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBCACHE-617) Pluggable optimistic conflict resolution

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-617?page=all ] Manik Surtani resolved JBCACHE-617. ----------------------------------- Fix Version/s: (was: 2.1.0.GA) Resolution: Rejected > Pluggable optimistic conflict resolution > ---------------------------------------- > > Key: JBCACHE-617 > URL: http://jira.jboss.com/jira/browse/JBCACHE-617 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.SP2 > Reporter: Galder Zamarreno > Assigned To: Manik Surtani > Priority: Minor > > Request for child node merge when conflict on Optimistic locking. > Conflicts include: children addition, removal and modification. > This would require JBossCache to abstract the conflict resolution and > enable customers to plugin their own rules on how to solve the conflicts. > This would be exposed as an API that customers could implement > according to their business rules. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBCACHE-617) Pluggable optimistic conflict resolution

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-617?page=all ] Manik Surtani reopened JBCACHE-617: ----------------------------------- > Pluggable optimistic conflict resolution > ---------------------------------------- > > Key: JBCACHE-617 > URL: http://jira.jboss.com/jira/browse/JBCACHE-617 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.SP2 > Reporter: Galder Zamarreno > Assigned To: Manik Surtani > Priority: Minor > > Request for child node merge when conflict on Optimistic locking. > Conflicts include: children addition, removal and modification. > This would require JBossCache to abstract the conflict resolution and > enable customers to plugin their own rules on how to solve the conflicts. > This would be exposed as an API that customers could implement > according to their business rules. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBCACHE-461) Potential bug in ReentrantWriterPreferenceReadWriteLock from util.concurrent

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-461?page=all ] Manik Surtani reopened JBCACHE-461: ----------------------------------- > Potential bug in ReentrantWriterPreferenceReadWriteLock from util.concurrent > ---------------------------------------------------------------------------- > > Key: JBCACHE-461 > URL: http://jira.jboss.com/jira/browse/JBCACHE-461 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.2.4, 1.2.4SP1 > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Minor > > Need to discuss on util.concurrent mail list. > See org.jboss.cache.lock.ReentrantWriterPreference2Readers1WriterLockTest -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-658) Fast locking for mostly-read PojoCache

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-658?page=all ] Manik Surtani closed JBCACHE-658. --------------------------------- Fix Version/s: (was: 2.1.0.GA) Resolution: Deferred > Fast locking for mostly-read PojoCache > -------------------------------------- > > Key: JBCACHE-658 > URL: http://jira.jboss.com/jira/browse/JBCACHE-658 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Legacy POJO Cache > Reporter: Nitzan Niv > Assigned To: Manik Surtani > > The locking mechanism locks all the nodes in the path from the tree root to the modified node. If the cache contains a deep hierarchy of nodes (e.g., PojoCache that contains complex objects) and the usage of the cache > is mostly-read the locking overhead is unnecessarilly large. > To enable REPEATABLE_READ isolation level with minimal overhead (but with reduced update parallelism) just the tree root should be locked instead of the nodes-path. To define this policy as a new isloation level ("single"): > Change in PessimisticLockInterceptor (line 199): > else { > if(isolation_level == IsolationLevel.SINGLE) {//XXX > if (i == 0) { > acquired=child_node.acquire(owner, lock_timeout, lock_type); > } > } else { > if(lock_type == DataNode.LOCK_TYPE_WRITE && i == (treeNodeSize - 1)) { > acquired=child_node.acquire(owner, lock_timeout, DataNode.LOCK_TYPE_WRITE); > } > else { > acquired=child_node.acquire(owner, lock_timeout, DataNode.LOCK_TYPE_READ); > } > }//XXX > } > in LockStrategyFactory.java: > if (lockingLevel == IsolationLevel.REPEATABLE_READ || lockingLevel == IsolationLevel.SINGLE) //XXX > return new LockStrategyRepeatableRead(); > and add the "SINGLE" isolation level to IsolationLevel.java. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBCACHE-658) Fast locking for mostly-read PojoCache

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-658?page=all ] Manik Surtani reopened JBCACHE-658: ----------------------------------- Assignee: Manik Surtani (was: Jason T. Greene) > Fast locking for mostly-read PojoCache > -------------------------------------- > > Key: JBCACHE-658 > URL: http://jira.jboss.com/jira/browse/JBCACHE-658 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Legacy POJO Cache > Reporter: Nitzan Niv > Assigned To: Manik Surtani > > The locking mechanism locks all the nodes in the path from the tree root to the modified node. If the cache contains a deep hierarchy of nodes (e.g., PojoCache that contains complex objects) and the usage of the cache > is mostly-read the locking overhead is unnecessarilly large. > To enable REPEATABLE_READ isolation level with minimal overhead (but with reduced update parallelism) just the tree root should be locked instead of the nodes-path. To define this policy as a new isloation level ("single"): > Change in PessimisticLockInterceptor (line 199): > else { > if(isolation_level == IsolationLevel.SINGLE) {//XXX > if (i == 0) { > acquired=child_node.acquire(owner, lock_timeout, lock_type); > } > } else { > if(lock_type == DataNode.LOCK_TYPE_WRITE && i == (treeNodeSize - 1)) { > acquired=child_node.acquire(owner, lock_timeout, DataNode.LOCK_TYPE_WRITE); > } > else { > acquired=child_node.acquire(owner, lock_timeout, DataNode.LOCK_TYPE_READ); > } > }//XXX > } > in LockStrategyFactory.java: > if (lockingLevel == IsolationLevel.REPEATABLE_READ || lockingLevel == IsolationLevel.SINGLE) //XXX > return new LockStrategyRepeatableRead(); > and add the "SINGLE" isolation level to IsolationLevel.java. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-718) PojoCache TxLockInterceptor needs to release the lock node as well

by Ben Wang (JIRA)

PojoCache TxLockInterceptor needs to release the lock node as well ------------------------------------------------------------------ Key: JBCACHE-718 URL: http://jira.jboss.com/jira/browse/JBCACHE-718 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Priority: Minor Fix For: 2.0.0 Currently, in TxLockInterceptor, I achieve the node lock by applying explicitly a cache.put(). It has two drawbacks: 1) It explicit going to insert a value to that node 2) Needs to do a remove when it is done. Not much can be done re: 1 now, but we should do 2, alhtough it will degrade the performance further. -- 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

16 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-754) RPC return values to use a marshaller as well

by Manik Surtani (JIRA)

RPC return values to use a marshaller as well --------------------------------------------- Key: JBCACHE-754 URL: http://jira.jboss.com/jira/browse/JBCACHE-754 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.4.0, 2.0.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0 Currently, all RPC calls go through the VersionAwareMarshaller which is responsible for efficiently marshalling JBC internal objects as well as user objects using JBoss Serialization. Return values and exceptions, on the other hand, are marshalled/unmarshalled using JGroups' Util.{to|from}ByteBuffer() which uses standard object serialization. The problems here are twofold: 1) Relatively inefficient (in speed as well as byte array size) marshalling/unmarshalling for return values 2) Potential class loader problems Most RPC calls in JBoss Cache do not have return values so this is not a problem that comes up often, but certain features (clustered cache loader, data gravitation in buddy replication) rely on return values. The solution to this problem is to be able to register a marshaller with the JGroups RPCDispatcher for return values (and exceptions) as well as for the RPC calls themselves. -- 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

16 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-788) Optimistic locking should not REQUIRE transactions!

by Manik Surtani (JIRA)

Optimistic locking should not REQUIRE transactions! --------------------------------------------------- Key: JBCACHE-788 URL: http://jira.jboss.com/jira/browse/JBCACHE-788 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.4.0, 1.3.0, 2.0.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0 Makes things simpler. TXs are only used so transaction workspaces can be stored in a transaction entry. This workspace can just as easily be stored in ThreadLocal for non-tx calls (that just have the lifespan of a single invocation). This will: 1) Make things a LOT quicker since we don't need 2PC for all calls. 2) Make the TxInterceptor a lot simpler 3) Allow the use of Opt Locking without a TM -- 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

16 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-932) Implicit lock ownership check in UnversionedNode

by Manik Surtani (JIRA)

Implicit lock ownership check in UnversionedNode ------------------------------------------------ Key: JBCACHE-932 URL: http://jira.jboss.com/jira/browse/JBCACHE-932 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA2 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.BETA2 This will involve read and write DIRECT methods on UnversionedNode to check whether the calling thread has acquired the necessary locks, else throw a lock exception. This will ensure proper concurrent access to the Node, even when not going through the interceptor stack. -- 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

16 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1129) Specify version dependencies in component-info.xml

by Brian Stansberry (JIRA)

Specify version dependencies in component-info.xml -------------------------------------------------- Key: JBCACHE-1129 URL: http://jira.jboss.com/jira/browse/JBCACHE-1129 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.0.0.GA Seems they are listed in pom.xml; need equivalent entries in component-info.xml. This adds fun, since we need to ensure consistency with the AS versions. -- 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

16 years, 11 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008