August 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBCACHE-224) Expose eviction management attributes

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-224?page=all ] Manik Surtani updated JBCACHE-224: ---------------------------------- Fix Version/s: (was: 2.0.0.GA) > Expose eviction management attributes > ------------------------------------- > > Key: JBCACHE-224 > URL: http://jira.jboss.com/jira/browse/JBCACHE-224 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Ben Wang > Priority: Minor > Original Estimate: 3 days > Remaining Estimate: 3 days > > We will need to expose the eviction side of management attributes. This is useful for troubleshooting. But keep in mind that it can also depends on the evction policy used as well. Basic ones are: > 1. How long does the eviction thread take to process the eviction each time? Or the aevergage time? > 2. What is the current capacity for the event queue? > 3. How many nodes have been evicted for this wakeup interval and what's the average time it takes? > 4. How many eviction miss? I.e., try to evict but the node is gone? -- 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

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-161) Support chain of CacheLoaders

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-161?page=all ] Manik Surtani updated JBCACHE-161: ---------------------------------- Fix Version/s: (was: 2.0.0.GA) > Support chain of CacheLoaders > ----------------------------- > > Key: JBCACHE-161 > URL: http://jira.jboss.com/jira/browse/JBCACHE-161 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.2.2 > Reporter: Bela Ban > Assigned To: Bela Ban > > E.g. TcpDelegatingCacheLoader --> JDBCCacheLoader > First try to find te element from a remote TCP-based Cache. If not found, go to the DB. Wrt storing, we could pick *any* or *all* CacheLoaders. -- 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

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (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 closed JBCACHE-461. --------------------------------- Resolution: Rejected May be superfluous with MVCC - JBCACHE-1151 - as this won't rely on lock upgrading at all. > 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 > Fix For: 2.1.0.GA > > > 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

18 years, 4 months

1
0
0 / 0

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

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-617?page=all ] Manik Surtani closed JBCACHE-617. --------------------------------- Resolution: Rejected Will be superfluous with MVCC - JBCACHE-1151 > 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 > Fix For: 2.1.0.GA > > > 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

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBCACHE-401) AOP Collection CacheSetImpl.add needs to be atomic

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-401?page=all ] Manik Surtani reassigned JBCACHE-401: ------------------------------------- Assignee: Jason T. Greene (was: Manik Surtani) > AOP Collection CacheSetImpl.add needs to be atomic > -------------------------------------------------- > > Key: JBCACHE-401 > URL: http://jira.jboss.com/jira/browse/JBCACHE-401 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PojoCache > Affects Versions: PojoCache > Reporter: Scott Marlow > Assigned To: Jason T. Greene > Fix For: 2.1.0.GA > > > CachedSetImpl.add() is not atomic (another thread could be adding the same value at the same time and both threads get past the existence test). > Current code looks like this: > public boolean add(Object o) > { > if(keySet().contains(o)) // existance test is done under separate lock > return false; > try { // putObject is done under separate lock > cache_.putObject(new Fqn(getFqn(), o),o); > return true; > } catch (CacheException e) { > throw new NestedRuntimeException(e); > } > } > I think we need to do something like this: > public boolean add(Object o) > { > try { > cache_.putIfAbsent(new Fqn(getFqn(), o),o); > return true; > } catch (CacheException e) { > throw new NestedRuntimeException(e); > } > } > Will need new api support -- 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

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-107) Extract locks from TreeCache into LockingTable

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-107?page=all ] Manik Surtani closed JBCACHE-107. --------------------------------- Resolution: Rejected Rejecting; this may be superfluous with MVCC/Striped locking designs for 3.0. > Extract locks from TreeCache into LockingTable > ---------------------------------------------- > > Key: JBCACHE-107 > URL: http://jira.jboss.com/jira/browse/JBCACHE-107 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 2.1.0.GA > > > Used by LockInterceptor and CreateIfNotExistsInterceptor -- 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

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-86) invalidate() across cluster on a per-region basis

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-86?page=all ] Manik Surtani updated JBCACHE-86: --------------------------------- Fix Version/s: 3.0.0 (was: 2.1.0.GA) > invalidate() across cluster on a per-region basis > ------------------------------------------------- > > Key: JBCACHE-86 > URL: http://jira.jboss.com/jira/browse/JBCACHE-86 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 1.2 > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 3.0.0 > > -- 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

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-65) Query on JBossCache

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-65?page=all ] Manik Surtani updated JBCACHE-65: --------------------------------- Fix Version/s: 4.0.0 (was: 3.0.0) Assignee: Manik Surtani (was: Bela Ban) > Query on JBossCache > ------------------- > > Key: JBCACHE-65 > URL: http://jira.jboss.com/jira/browse/JBCACHE-65 > Project: JBoss Cache > Issue Type: Feature Request > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 4.0.0 > > > XPath ? -- 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

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-70) Make JBossCache an XAResource

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-70?page=all ] Manik Surtani updated JBCACHE-70: --------------------------------- Fix Version/s: 3.2.0 (was: 3.0.0) > Make JBossCache an XAResource > ----------------------------- > > Key: JBCACHE-70 > URL: http://jira.jboss.com/jira/browse/JBCACHE-70 > Project: JBoss Cache > Issue Type: Feature Request > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 3.2.0 > > -- 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

18 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-60) Partitioned Cache

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-60?page=all ] Manik Surtani updated JBCACHE-60: --------------------------------- Fix Version/s: 3.2.0 (was: 3.0.0) > Partitioned Cache > ----------------- > > Key: JBCACHE-60 > URL: http://jira.jboss.com/jira/browse/JBCACHE-60 > Project: JBoss Cache > Issue Type: Feature Request > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 3.2.0 > > Original Estimate: 10 weeks > Remaining Estimate: 10 weeks > > - Distributed load across multiple nodes in a cluster > - No replication/redundancy -- 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

18 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2007