> From: Ken Bowen [mailto:[EMAIL PROTECTED] > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
