Thanks Kristian for reporting this issue and thanks Kedar for the help!
Judy
Kristian Rink wrote:
> Hi Kedar, *;
>
> Kedar Mhaswade schrieb:
>> AFAIK, the changes are dynamically applicable. Are you saying that it's
>> the case with only activation module logger or all the loggers? IOW,
>> this is supposed to work just like it did in v2.
>
> I just filed
>
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=11496 ,
>
> wrote down my insights and attached a simple test case to make it
> reproducible. It seems, in my environment, after using "asadmin
> set-log-level" on v3, it takes a domain restart to make the changes
> actually effective, even though the "updated log levels for loggers"
> is written out to the log after doing so.
>
>
>
>> So, this dynamic reconfiguration capability is important to you, right?
>
> Yes, definitely. :) At the moment (gfv2) we just run our apps in
> WARNING mode and tend to switch logging to a finer mode in situations
> in which we see an actual error or problem reported by either internal
> or external users. Restarting the domain usually is not an option in
> these situations, even less with gfv3 (as I noticed starting up gfv3
> domain, running the same apps we have deployed to gfv2, takes a bit
> longer).
>
>
>
>> Can you try it with the vanilla logging (JDK logging) that comes by
>> default?
>
> Did so, please have a look at the issue text. :) Basically, as slf4j
> is "just" some sort of facade to various logging implementations
> (similar to commons-logging, just a little more "reliable" it seems),
> I wasn't supposing it to cause this problem, and actually, my
> experiments showed it's not the fault of slf4j :)
>
> Cheers & all the best,
> Kristian
>
>