Quick correction:
# For example, set the com.xyz.foo logger to only log SEVERE
# messages:
#org.apache.catalina.startup.ContextConfig.level = FINE
#org.apache.catalina.startup.HostConfig.level = FINE
#org.apache.catalina.session.ManagerBase.level = FINE
Should the left side of the equal sign be
Ole Ersoy schrieb:
Hi,
I would really appreciate it if someone could elaborate on the case for
these logging properties:
# Facility specific properties.
# Provides extra control for each logger.
#
Rainer Jung wrote:
SNIP
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager]
is the name of a logger, in this case the name of the logger associated
with the context /manager in host localhost in Engine Catalina.
Most loggers get their names from class names, but context
Ole Ersoy schrieb:
Rainer Jung wrote:
SNIP
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager]
is the name of a logger, in this case the name of the logger
associated with the context /manager in host localhost in Engine
Catalina.
Most loggers get their names from class
> From: Rainer Jung [mailto:[EMAIL PROTECTED]
> Subject: Re: [Logging] Facility Specific Properties
>
> > if (myLogger.getLevel() >= Level.WARNING)
> > {
> > myLogger.warn('This is a warning'); }
>
> More precisely:
>
> if (log.isDebugEnable
SNIP
Close to that. Since "Catalina" and "localhost" are names of elements in
server.xml, and those names can be changed, this logger name is
generated dynamically. So you won't find it verbosely in the code. Look
at method logName() in ContainerBase.java.
Thanks for the tip - I will do.
No
Ole Ersoy wrote:
No, the call log.info(SOMETHING) will need to calculae something,
before it really calls the error method of the logger, which then
immediately might notice, that the configured log level doesn't allow
handling an info message.
Now SOMETHING is quite often not a simple string
SNIP
I think one of the confusing things about the current logging environment is
the lack of documentation about the mapping between commons-logging and
java.util.logging levels and APIs, as implemented by JULI. For example, c-l
has six logging levels, whereas as j.u.l has seven; some of th
SNIP
No it would grab the logger for the context, which will automatically be
the one for [/mywebapp] and not [/manager]. It can't log to the logger
of another context. Look at javax.servlet.ServletContext.log().
OOh - OK - The gears are starting to turn...maybe. The context logger confi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ole,
Ole Ersoy wrote:
| I hope the mappings are all inclusive from java.util.logging's
| perspective so that if I set the a level to INFO I get info, plus
| possibly some other level's that are greater than INFO? In other words
| something that shou
day, June 23, 2008 8:17 PM
Subject: Re: [Logging] Facility Specific Properties
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ole,
Ole Ersoy wrote:
| I hope the mappings are all inclusive from java.util.logging's
| perspective so that if I set the a level to INFO I get info, plus
| possibly some
Super - Thanks for the elaboration!
- Ole
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ole,
Ole Ersoy wrote:
| I hope the mappings are all inclusive from java.util.logging's
| perspective so that if I set the a level to INFO I get info, plus
| possibly some other l
Martin wrote:
Found this helpful
http://tomcat.apache.org/tomcat-5.5-doc/logging.html
default logging is commons-logging with known limitation to Engines and
Hosts
this limitation of JDK Logging appears to be the genesis of per-web
application logging as the configuration is per-VM
That sou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ole,
Ole Ersoy wrote:
| From what I understand Tomcat 6 logging has been overhauled and the
| java.util.logging implementation was replaced with JULI, which
| understands how to load per web app configuration files and make the
| corresponding confi
| From what I understand Tomcat 6 logging has been overhauled and the
| java.util.logging implementation was replaced with JULI, which
| understands how to load per web app configuration files and make the
| corresponding configuration available via the LogManager to the web app.
I think that ha
> From: Ole Ersoy [mailto:[EMAIL PROTECTED]
> Subject: Re: [Logging] Facility Specific Properties
>
> Good catch! I just checked the 5.5 documentation and it's
> the same as Tomcat 6.
Not quite. The procedure for replacing java.util.logging with log4j is a bit
differe
16 matches
Mail list logo
