Re: Issues with java.util.logging
Scott Ferguson <[email protected]> Tue, 6 Jun 2006 16:00:20 -0700
| Newsgroups | gmane.text.xml.resin.user |
|---|---|
| Message-ID | <[email protected]> |
On Jun 6, 2006, at 2:54 PM, Earl, Michael wrote:
> Hello All,
>
> We recently migrated from Tomcat to Resin. We are now discovering
> that for some reason ALL of our classes are creating log messages
> at ALL levels. This did not happen nor does it still happen with
> Tomcat -- with the same code. We love Resin by the way so this is
> not a complaint. I am seeking to understand why this is
> happening. I have added the following to our resin config file:
>
> <logger name="com.hp.sfng" level="info" path='stdout:' timestamp='[%
> H:%M:%S.%s] '/>
>
> This had no effect, all classes are sending log messages.
Can you give a sample of how you're allocating and using the Logger?
Our standard pattern is:
package com.caucho.foo;
public class Bar {
private static final Logger log = Logger.getLogger
(Bar.class.getName());
Then we use
log.info - stuff users should see
log.finer - stuff application writers will want to see to help
debugging
log.finest - more details for us to debug, but which may be
cryptic to outside developers
-- Scott
> Thanks for any help,
>
> Mike.
>
> ---------------------------------------------------
> Michael Earl “For whoever exalts
> Software Engineer himself will be humbled,
> GO-IT MBP/SF and whoever humbles
> Bldg R4 himself will be exalted.”
> HP, Roseville CA
> +1-916-748-7958 work Matthew 23:12
> +1-916-671-4466 cell
> ---------------------------------------------------
>