August 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Reopened: (JBCACHE-5) AOP HTTP session replication under Tomcat 5

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-5?page=all ] Manik Surtani reopened JBCACHE-5: --------------------------------- Assignee: (was: Ben Wang) > AOP HTTP session replication under Tomcat 5 > ------------------------------------------- > > Key: JBCACHE-5 > URL: http://jira.jboss.com/jira/browse/JBCACHE-5 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 2.0.0.GA > Reporter: Bela Ban > Fix For: 2.0.0.GA > > Original Estimate: 10 weeks > Remaining Estimate: 10 weeks > > - JBossCache with aop/aopc > - Implemented any required features to 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, 9 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBCACHE-35) Externalize the buffer queue size in LRUAlgorithm

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-35?page=all ] Manik Surtani reopened JBCACHE-35: ---------------------------------- Assignee: (was: Manik Surtani) > Externalize the buffer queue size in LRUAlgorithm > ------------------------------------------------- > > Key: JBCACHE-35 > URL: http://jira.jboss.com/jira/browse/JBCACHE-35 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 1.2 > Reporter: Ben Wang > Priority: Minor > Fix For: 2.0.0.GA > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Currently, the LRUAlgorithm use a hard size of 5000 on the buffer queue to process node eviction. We should make this configurable so it can adapt to different enviornment. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-830) Incorrect serialization of Collection and Map proxies

by Brian Stansberry (JIRA)

Incorrect serialization of Collection and Map proxies ----------------------------------------------------- Key: JBCACHE-830 URL: http://jira.jboss.com/jira/browse/JBCACHE-830 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 1.2.4SP2 Reporter: Brian Stansberry Assigned To: Ben Wang The PojoCache Collection and Map proxies implement Serializable via List but don't do anything to override default serialization. They have non-transient fields with refs to things like the cache itself, so serializing one of these is a big problem -- you serialize the whole cache. Not sure what the best solution to this is. Perhaps use writeReplace()? -- 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, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBCACHE-774) PojoCache to use a RPC layer to transmit POJO events

by Ben Wang (JIRA)

PojoCache to use a RPC layer to transmit POJO events ---------------------------------------------------- Key: JBCACHE-774 URL: http://jira.jboss.com/jira/browse/JBCACHE-774 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Priority: Critical Fix For: PojoCache 2.1.0 Currently, the POJO events does not propagate to other nodes since there is no way to do that. We will need some specific RPC mechanism to that such that we can broadcast POJO attach, detach, and modification events. This will also help to remove the POJO cache interceptor on the remote node as well. -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Updated: (JBCACHE-237) When remove a Pojo with shared Collection instances from cache, will need to restore the original reference

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-237?page=all ] Manik Surtani updated JBCACHE-237: ---------------------------------- Fix Version/s: (was: 2.0.0.GA) > When remove a Pojo with shared Collection instances from cache, will need to restore the original reference > ----------------------------------------------------------------------------------------------------------- > > Key: JBCACHE-237 > URL: http://jira.jboss.com/jira/browse/JBCACHE-237 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: PojoCache > Affects Versions: 1.2.3 > Reporter: Ben Wang > Assigned To: Ben Wang > Original Estimate: 1 week > Remaining Estimate: 1 week > > Currently when Pojos that share Collection instances (e.g., a List sub-object), during putObject operation, it will be replaced by a corresponding proxy at runtime. But when removeObject is called, we will need to restore the original reference instead of still using the dynamic proxy one. That is we need to ditch the dynamic proxy reference. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-990) PojoCache leaks memory

by Manik Surtani (JIRA)

PojoCache leaks memory ---------------------- Key: JBCACHE-990 URL: http://jira.jboss.com/jira/browse/JBCACHE-990 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 2.0.0.ALPHA2, 2.0.0.BETA1 Reporter: Manik Surtani Assigned To: Jason T. Greene Priority: Critical Fix For: 2.0.0.BETA2 I've included the test from the forum thread into tests/perf/org/jboss/cache/manualtests/PojoCacheMemoryLeakTest.java - note that since this is in the "manualtests" package, it will not be run by cruise control. When running from within my IDE, after about 8 loops it bombs with an OOME. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Updated: (JBCACHE-561) Create a separate META-INF sub-directory for PojoCache

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-561?page=all ] Manik Surtani updated JBCACHE-561: ---------------------------------- Fix Version/s: (was: 2.0.0.GA) > Create a separate META-INF sub-directory for PojoCache > ------------------------------------------------------ > > Key: JBCACHE-561 > URL: http://jira.jboss.com/jira/browse/JBCACHE-561 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Jason T. Greene > Priority: Minor > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Separate the PojoCache configuration from regular TreeCache so that user don't get confused. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-933) PojoCache to create a cache wrapper to retry when upgradeexception is encountered

by Ben Wang (JIRA)

PojoCache to create a cache wrapper to retry when upgradeexception is encountered --------------------------------------------------------------------------------- Key: JBCACHE-933 URL: http://jira.jboss.com/jira/browse/JBCACHE-933 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0.BETA1 Current 2.0 release becuase of lock contention on __JBossInternal__, it becomes much more common to have lock UpgradeException. Solutions are: 1. Fix the underlying cache lock algorithm to allow lock upgrade. This can be tricky since it affects lots of other codes. 2. Re-try the logic in a Cache wrapper when UpgradeException is encountered. I think option #2 is the best route now. -- 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, 9 months

3
5
0 / 0

[JBoss JIRA] Updated: (JBCACHE-204) Externalize RegionManager.Capacity parameter

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-204?page=all ] Manik Surtani updated JBCACHE-204: ---------------------------------- Fix Version/s: (was: 2.0.0.GA) > Externalize RegionManager.Capacity parameter > -------------------------------------------- > > Key: JBCACHE-204 > URL: http://jira.jboss.com/jira/browse/JBCACHE-204 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Ben Wang > Priority: Minor > Original Estimate: 3 days > Remaining Estimate: 3 days > > RegionManager.CAPACITY is used to determine the size of the eviction event queue. It is fixed now. We should externalize it later such that we can tune the eviction policy performance. E.g., when the load is heavy, we may need to increase the queue size such that it is not blocking. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-479) Cache loader to load children as well when loading a node

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-479?page=all ] Manik Surtani updated JBCACHE-479: ---------------------------------- Fix Version/s: (was: 2.0.0.GA) > Cache loader to load children as well when loading a node > --------------------------------------------------------- > > Key: JBCACHE-479 > URL: http://jira.jboss.com/jira/browse/JBCACHE-479 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.2.4SP1 > Reporter: Manik Surtani > Assigned To: Ben Wang > > Requested by Ben, for failing unit test o.j.c.aop.loader.FileCacheLoaderAopCollectionsTest -- 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, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2007