So until this bug is fixed,
FINE needs to be set in logging.properties (of GlassFish, not JDK_HOME
right?) and for that specific logger ?
How do I know the logger corresponding to the property
"eclipselink.logging.level" set in persistence.xml ?
A noob question ...
Is there a hierarchy of logger, for example:
javax.enterprise.system.*=FINE
and then everything under this domain is FINE logging as well.
Also, I agree with Peter that default FINE level may dump lot more
messages than required by an average user.
-Arun
Carla Mott wrote:
> That's right. You may have to restart the server for this to take
> affect. Also you will need to set the appropriate logger to the FINE
> level too. At the point you don't want to see the messages you just set
> the logger level to INFO again. Soon I will update logging.properties to
> set the console level to FINEST by default.
>
> carla
>
> Marina Vatkina wrote:
>> It's a bug: https://glassfish.dev.java.net/issues/show_bug.cgi?id=7512
>> but there is a work around (that I didn't try): in the
>> logging.properties file set
>>
>> java.util.logging.ConsoleHandler.level=FINE
>>
>> Regards,
>> -marina
>>
>> Arun Gupta wrote:
>>> "asadmin start-domain --verbose" does not show FINE+ log messages.
>>> This is with b43 and might have been happening earlier as well.
>>>
>>> Is that intentional ?
>>>
>>> Can I override it ?
>>>
>>> -Arun
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
--
Application Platform, Sun Microsystems, Inc.
Blog: http://blogs.sun.com/arungupta