March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-885) Bug when calling putObject() with array as argument

by Bela Ban (JIRA)

Bug when calling putObject() with array as argument --------------------------------------------------- Key: JBCACHE-885 URL: http://jira.jboss.com/jira/browse/JBCACHE-885 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Reporter: Bela Ban Assigned To: Ben Wang Should at least not lead to an exception, we could for example state that we don't support arrays yet. To reproduce: TreeCacheAop cache; long arr=new long[]{1,2}; cache.putObject("arr", arr); -- 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
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-806) Invalidation causes problems with otimistic data versioning and certain edge cases

by Manik Surtani (JIRA)

Invalidation causes problems with otimistic data versioning and certain edge cases ---------------------------------------------------------------------------------- Key: JBCACHE-806 URL: http://jira.jboss.com/jira/browse/JBCACHE-806 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Replication Affects Versions: 1.4.0.SP1 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 Related to JBCACHE-793, but that has more to do with fixing the recommended configurations. >From email conversations: Manik >> At the moment, if I do a put() with V1 into CacheA, this sends an invalidation msg to CacheB. If CacheB has V2 already, the invalidation will fail. What you are saying is, this failure should propagate back to CacheA so the put() with V1 will also fail and this will not exist in CacheA's memory. Am I correct? Max >> It wasn't the scenario I had in mind, but this one is probably also relevant. Manik >> Or is the scenario you're trying to paint more like: V2 put into CacheA. CacheB has V1, gets the invalidation msg, and V1 is evicted. Someone now calls a put() on CacheB with V1, and you are afraid this will be written into the cache? This is true, the invalidation back to CacheA will fail, but CacheB will have stale data in the cache. Max >> This is the scenario I had in mind yes. -- 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
14
0 / 0

[JBoss JIRA] Created: (JBCACHE-912) Fix tutorial

by Manik Surtani (JIRA)

Fix tutorial ------------ Key: JBCACHE-912 URL: http://jira.jboss.com/jira/browse/JBCACHE-912 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 1.4.1.GA -- 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

4
7
0 / 0

[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, 9 months

3
7
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-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] 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] 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] Created: (JBCACHE-706) Integrate JMX bindings of JBoss Cache and PojoCache with AS5 and MC

by Manik Surtani (JIRA)

Integrate JMX bindings of JBoss Cache and PojoCache with AS5 and MC ------------------------------------------------------------------- Key: JBCACHE-706 URL: http://jira.jboss.com/jira/browse/JBCACHE-706 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 This will involve: 1. Adding new JMX MBean interface (is this necessary for the MC? What about standalone use?) 2. Providing sample XML files 3. Updating documentation -- 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
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1004) Genericize POJO API

by Jason T. Greene (JIRA)

Genericize POJO API ------------------- Key: JBCACHE-1004 URL: http://jira.jboss.com/jira/browse/JBCACHE-1004 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Jason T. Greene Assigned To: Jason T. Greene Fix For: 2.0.0.GA Use generics where possible and logical -- 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
2
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 March 2007