开发者

Tomcat App says "Unable to configure the logging system. No log.properties was found."

开发者 https://www.devze.com 2022-12-10 00:36 出处:网络
I have an embedded tomcat app and whenever I start it up I see this error printed to the console twice:

I have an embedded tomcat app and whenever I start it up I see this error printed to the console twice:

Unable to configure the logging system.  No log.properties was found.

It seems stupid, but I've done some googling and searched stackoverflow and can't seem to find someone experiencing this problem.

My main class Looks roughly like this:

public class AuthServerEntryPoint {
  static {
    org.apache.log4j.PropertyConfigurator.configure("conf/log4j.properties");
  }
public static void main(String[] args) {
  // ...
}

"conf/log4j.properties" contains a seemingly valid configuration:

log4j.appender.mainAppend=org.apache.log4j.ConsoleAppender
log4j.appender.mainAppend.layout=org.apache.log4j.PatternLayout
log4j.appender.mainAppend.layout.ConversionPattern=%d %p [%t] %c -- %m%n 

log4j.appender.fileAppend=org.apache.log4j.FileAppender
log4j.appender.fileAppend.layout=org.apache.log4j.PatternLayout
log4j.appender.fileAppend.layout.ConversionPattern=%d %p [%t] %c - %m%n 
log4j.appender.fileAppend.file=logs/myservice.log

log4j.rootLogger = info, fi开发者_运维知识库leAppend
log4j.logger.com.mycompany.myservice = debug, fileAppend

And the logging actually does work - i.e., logs are correctly written to myservice.log. So what gives?

Thanks! -Carl


By embedded Tomcat app, do you mean that you are starting Tomcat from Java code and are using the class org.apache.catalina.startup.Embedded?

If yes, my guess is that Tomcat might not be able to find its logging configuration file that is set up in catalina.sh (or equivalent) when using the scripts:

LOGGING_CONFIG="-Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties"

The odd part is that this file is called logging.properties, not log.properties, so I'm really not sure. I didn't check Tomcat sources though, maybe they are doing some kind of black magic in there.

Could you just try to rename $CATALINA_BASE/conf/logging.properties into log.properties (or not) and to put it on the classpath of your app (or to set -Djava.util.logging.config.file)?


By default, log4j will look for a logging properties file on the classpath. Put your webapp's logging properties config file into its WEB-INF/classes directory; e.g.

$CATALINA_HOME/webapps/<yourApp>/WEB-INF/classes/log4j.properties

This is the simple approach to getting a webapp to use Log4j is recommended by the referenced documentation. And it is the approach I use myself for webapp logging.

There are various other ways to configure Log4j logging on Tomcat as well. It is possible that your Tomcat has been (partly) configured to use one of them, but something has not been done quite right.

Configuring Tomcat' log4j logging via the system properties is an option that avoids figuring out where log4j is looking ... and what is going wrong. But you are then stuck with creating/using a custom launch script or having to remember to set environment variables before launching Tomcat.

References:

  • Configuring logging on Tomcat 5.5
  • Configuring logging on Tomcat 6
  • The "Default Initialization under Tomcat" section of the Log4j Manual
0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号