Hi,
On Thu, Aug 18, 2016 at 10:12 PM, Tanya Madurapperuma
wrote:
>
>
> 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
>> wrote:
>>
>>> This warning is coming from shindig which is the u
+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, Mohanada
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
> wrote:
>
>> This warning is coming from shindig which is the underlying library that
>> we used for gadget rendering and is a 3rd party library. Q
On Thu, Aug 18, 2016 at 3:55 PM, Tanya Madurapperuma 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
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]
[
[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 wrote:
> Hi DS team,