Controlling JULI logging 1) Tomcat on its own; 2) when running under Eclipse.

[Ken Bowen <kb...@als.com>]

I'm using a freshly unzipped install of Tomcat 5.5.25 on Windows.
1) JULI logging is automatically enabled, and is controlled by the 
logging.properties file found in conf.
This seems to be at variance with the statement in 
http://tomcat.apache.org/tomcat-5.5-doc/logging.html :
        " Example logging.properties file to be placed in common/classes:"
The provided example is exactly what is shipped in conf.
Is control from the location in conf the correct way to do it (i.e., I 
shouldn't move it to common/classes)?
Does conf/logging.properties override common/classes/logging.properties, 
or the other way around?

2) I'm using Eclipse/MyEclipse for development.  It /seems/ to log 
according to the shipped conf/logging.properties.
However, running under Eclipse appears to be immune to any changes in 
conf/logging.properties, and
also to placing a changed logging.properties in common/classes, as if 
Eclipse were keeping its own
private copy.   Is this in fact the case?  If so, is there any way to 
control it?  I couldn't find anything
in the MyEclipse doc.  I'm hoping someone here knows about this.

Thanks in advance.
Ken




---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

RE: Controlling JULI logging 1) Tomcat on its own; 2) when running underEclipse.

["Caldarale, Charles R" <Ch...@unisys.com>]

> From: Ken Bowen [mailto:kbowen@als.com] 
> Subject: Controlling JULI logging 1) Tomcat on its own; 2) 
> when running underEclipse.
> 
> 1) JULI logging is automatically enabled, and is controlled by the 
> logging.properties file found in conf.
> This seems to be at variance with the statement in 
> http://tomcat.apache.org/tomcat-5.5-doc/logging.html :
> " Example logging.properties file to be placed in common/classes:"

The doc is not incorrect, but it is slightly incomplete.  You can place
a logging.properties file in each classloader's classes directory,
including the one for common; this will control the logging for any
classes loaded by that classloader.  If there is no logging.properties
file in a particular classes directory, that classloader will use the
one defined by the java.util.logging.config.file system property; the
default value is conf/logging.properties, set by catalina.bat or the
service installer.

> However, running under Eclipse appears to be immune to any changes in 
> conf/logging.properties

I don't use Eclipse, but perhaps it has set
java.util.logging.config.file to point somewhere else.  If you deploy
Lambda Probe (www.lambdaprobe.org), it can show you what the value of
all the system properties are for the running Tomcat.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org