+1 For disabling that at log4j level if possible. Since it is harmless if we can hide the log or stop printing the log repetitively that would be so much better.
Sewmini Jayaweera *Software Engineer - QA Team* Mobile: +94 (0) 773 381 250 sewm...@wso2.com On Thu, Aug 18, 2016 at 9:18 PM, Mohanadarshan Vivekanandalingam < mo...@wso2.com> wrote: > > > On Thu, Aug 18, 2016 at 3:55 PM, Tanya Madurapperuma <ta...@wso2.com> > wrote: > >> This warning is coming from shindig which is the underlying library that >> we used for gadget rendering and is a 3rd party library. Quick solution for >> this is to increase maxDepth value as mentioned in [1] by Mohan. >> If not we will have to analyze EhCache memory for memory consuming >> objects [2] [3] >> >> [1] https://wso2.org/jira/browse/ANLYIS-48 >> [2] https://cwiki.apache.org/confluence/display/SHINDIG/Debuggin >> g+EhCache's+SizeOfEngine >> [3] https://cwiki.apache.org/confluence/display/SHINDIG/EhCache+ >> Memory+Analysis >> > > @Tanya, Thanks for the response.. I think, increasing the maxDepth value > is not helpful all the time.. Whether you guys, explored about this more ? > Since it is observed in various products/cases. If this log does not > reflect any useful info then can, we disable that at log4j level ? > > Thanks, > Mohan > > >> >> Thanks, >> Tanya >> >> On Thu, Aug 18, 2016 at 3:40 PM, Mohanadarshan Vivekanandalingam < >> mo...@wso2.com> wrote: >> >>> [Moving to DEV] >>> >>> Related UES/DS jira is [1].. >>> >>> @Sewmini, above logs are only printed once for a user (When loading a >>> gadget for first time - once for each gadget).. >>> >>> [1] https://wso2.org/jira/browse/UES-658 >>> >>> >>> Thanks, >>> Mohan >>> >>> >>> On Thu, Aug 18, 2016 at 3:34 PM, Sewmini Jayaweera <sewm...@wso2.com> >>> wrote: >>> >>>> Hi DS team, >>>> >>>> I observed the same issue reported in [1] in the latest Analytics pack >>>> given. I reopened the issue since repeatedly printed warning may mislead >>>> user thinking it's a critical issue eve,n though it is harmless and it >>>> doesn't give a good impression to the user. >>>> >>>> It would be great if we can get this fixed. If it is difficult to fix >>>> it in this release can we change it to an improvement and fix it later >>>> without having it as won't fix? >>>> >>>> [1]. https://wso2.org/jira/browse/ANLYIS-48 >>>> >>>> Thank you in advance. >>>> Kind regards, >>>> >>>> Sewmini Jayaweera >>>> *Software Engineer - QA Team* >>>> Mobile: +94 (0) 773 381 250 >>>> sewm...@wso2.com >>>> >>> >>> >>> >>> -- >>> *V. Mohanadarshan* >>> *Associate Tech Lead,* >>> *Data Technologies Team,* >>> *WSO2, Inc. http://wso2.com <http://wso2.com> * >>> *lean.enterprise.middleware.* >>> >>> email: mo...@wso2.com >>> phone:(+94) 771117673 >>> >> >> >> >> -- >> Tanya Madurapperuma >> >> Senior Software Engineer, >> WSO2 Inc. : wso2.com >> Mobile : +94718184439 >> Blog : http://tanyamadurapperuma.blogspot.com >> > > > > -- > *V. Mohanadarshan* > *Associate Tech Lead,* > *Data Technologies Team,* > *WSO2, Inc. http://wso2.com <http://wso2.com> * > *lean.enterprise.middleware.* > > email: mo...@wso2.com > phone:(+94) 771117673 >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
