Peter Williams wrote:
> Only tangentially related to your question, but is this particular
> logging level dynamically changeable via admin GUI/asadmin?
Not for Prelude. The solution is to edit logging.properties while
server is running, right Carla?
If not,
> should it be?
Yes, for v3 final, because this is how it was for V2.
>
> If it is dynamically changeable and has been passed to the runtimes,
> then they will need to be notified of the change, or restarted if
> notification is not workable.
>
> -Peter
>
> Kedar Mhaswade wrote:
>>
>>
>> Jacob Kessler wrote:
>>> I'm trying to find the current logging level so that I can pass it on
>>> to a Jruby runtime to let Rails/merb/etc. log things correctly and
>>> sensibly. However, a simple call to logger.getLevel() on the logger I
>>> have in Java returns a null which, while allowed, isn't very useful.
>>> Trying to recuse myself up the logger hierarchy until I find a
>>> non-null level seems like the wrong way to deal with that, so I
>>> thought I'd ask here: Is there a simple way to find out the current
>>> log level that your logger is logging at?
>>
>> asadmin generate-jvm-report --type=log | grep <logger name>?
>>
>> -Kedar
>>
>> (Assuming v3 Prelude).
>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>