[JBoss JIRA] Created: (JBCACHE-739) Exception in a CacheLoader throws ChainingCacheLoader calling method and prevent the call to the next CacheLoaders
by shimi k (JIRA)
Exception in a CacheLoader throws ChainingCacheLoader calling method and prevent the call to the next CacheLoaders
-------------------------------------------------------------------------------------------------------------------
Key: JBCACHE-739
URL: http://jira.jboss.com/jira/browse/JBCACHE-739
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Cache loaders
Affects Versions: 1.4.0
Reporter: shimi k
Assigned To: Manik Surtani
Fix For: 2.0.0
All the delegate methods in ChainingCacheLoader throws Exceptions. Each one of the methods iterates on all the configured Cacheloader.
public void put(Fqn name, Map attributes) throws Exception
{
Iterator i = writeCacheLoaders.iterator();
while (i.hasNext())
{
CacheLoader l = (CacheLoader) i.next();
l.put(name, attributes);
}
}
Since the methods throws an Exception, Exception in one of the CacheLoaders will throw the thread out of the method. If the Exception will happen before the last CacheLoader, the ChainingCacheLoader will not call the other CachLoaders.
--
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, 12 months
[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, 12 months
[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, 12 months