Hi Henry, I am unable to reproduce the issue with those gadgets in the sample common container. If you have some spare time, can you try to turn on the logging I linked to and check the "getUserFilter" call to ensure that the user filter is being loaded properly?
If that filter file isn't being loaded properly then you'll see those warnings. It might be worth sanity checking that this file is in your local environment: shindig-common/src/main/resources/org/apache/shindig/common/cache/ehcache/SizeOfFilter.txt Thanks, -Stanton From: Henry Saputra <[email protected]> To: [email protected], Date: 06/04/2012 14:30 Subject: Re: Seeing WARNING messages related to ehcache Hi Stanton, Its also reproducible in Shindig trunk if you open the pubsub or activity stream sample gadgets. - Henry On Sun, Jun 3, 2012 at 11:06 AM, Stanton Sievers <[email protected]> wrote: > Hi Henry, > > Yes, these are related to the recent EhCache upgrades. Do you know when > these warnings were logged? Can you reproduce it using any of the samples > in Shindig? The issue is related to the code in ehcache that tries to > calculate object size by walking the object graph. > > More info here: > https://cwiki.apache.org/confluence/display/SHINDIG/Debugging+EhCache%27s+SizeOfEngine > > Thanks, > -Stanton > > > > From: Henry Saputra <[email protected]> > To: [email protected], > Date: 06/03/2012 01:49 > Subject: Seeing WARNING messages related to ehcache > > > > HI Guys, > > I am start seeing these WARNING messages related to ehcache: > > Jun 2, 2012 10:46:26 PM net.sf.ehcache.pool.sizeof.SizeOf deepSizeOf > WARNING: The configured limit of 1,000 object references was reached > while attempting to calculate the size of the object graph. This can > be avoided by adding stop points with @IgnoreSizeOf annotations. Since > the CacheManger or Cache <sizeOfPolicy> elements > maxDepthExceededBehavior is set to "abort", the sizing operation has > stopped and the reported cache size is not accurate. If performance > degradation is NOT an issue at the configured limit, raise the limit > value using the CacheManager or Cache <sizeOfPolicy> elements maxDepth > attribute. For more information, see the Ehcache configuration > documentation. > Jun 2, 2012 10:46:58 PM net.sf.ehcache.pool.sizeof.SizeOf deepSizeOf > WARNING: The configured limit of 1,000 object references was reached > while attempting to calculate the size of the object graph. This can > be avoided by adding stop points with @IgnoreSizeOf annotations. Since > the CacheManger or Cache <sizeOfPolicy> elements > maxDepthExceededBehavior is set to "abort", the sizing operation has > stopped and the reported cache size is not accurate. If performance > degradation is NOT an issue at the configured limit, raise the limit > value using the CacheManager or Cache <sizeOfPolicy> elements maxDepth > attribute. For more information, see the Ehcache configuration > documentation. > > Could this be related to ehcache upgrade in Shindig trunk happened > recently? > > - Henry > >
