I am not sure this is coming form UES side, more likely it's some DAS code since error is coming from Ehcache. please ping when you see this.
On Mon, Sep 14, 2015 at 8:31 PM, Gokul Balakrishnan <[email protected]> wrote: > UES team, any suggestions for this? > > > On Thursday, 10 September 2015, Gokul Balakrishnan <[email protected]> wrote: > >> Hi UES team, >> >> We're seeing the following warning repeatedly when accessing the >> dashboard, seems this has been known for a while. Are there any adverse >> effects, or is it OK to hide this warn from the console? >> >> [2015-09-10 17:34:26,149] WARN {net.sf.ehcache.pool.sizeof.SizeOf} - >> 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. >> >> Thanks, >> >> -- >> Gokul Balakrishnan >> Senior Software Engineer, >> WSO2, Inc. http://wso2.com >> Mob: +94 77 593 5789 | +1 650 272 9927 >> > > > -- > Gokul Balakrishnan > Senior Software Engineer, > WSO2, Inc. http://wso2.com > Mob: +94 77 593 5789 | +1 650 272 9927 > > -- With regards, *Manu*ranga Perera. phone : 071 7 70 20 50 mail : [email protected]
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
