river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gregg Wonderly <gr...@wonderly.org>
Subject Re: [jira] Commented: (RIVER-13) net.jini.discovery.LookupDiscovery logging is verbose and distracting to debugging
Date Sun, 04 Mar 2007 23:20:25 GMT
Mark Brouwer wrote:
> Assume we change the hierarchy from:
> 
>   n.j.d.LookupDiscovery
> 
> to
> 
>   n.j.d.LookupDiscovery.eth0.unicast
>   n.j.d.LookupDiscovery.eth0.multicast
>   n.j.d.LookupDiscovery.eth1.unicast
>   n.j.d.LookupDiscovery.eth1.multicast
> 
> and I want to apply a filter so that only log record with a level of
> exactly FINEST are logged for discovery then I can't no longer apply
> that filter on the logger named "LookupDiscovery".

The existing implementation of the java.util.logging allows you to say

net.jini.discovery.LookupDiscovery.level=FINEST

and that covers all in the hierarchy of names beyond that name.  Are you 
referring to your filter mechanism that doesn't match the hierarchy?

Also, my logman.dev.java.net project has an example formatter that is used for 
logrecords displayed in its serviceUI.  One setting of properties for the 
formatter causes it to display [n.j.d.LookupDiscovery].  It uses the first 
letter of all the components of the name except the last to shorten the display 
width.

Gregg Wonderly

Mime
View raw message