Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have been seeing this for literally years as part of tomcat apps, and now that I have gone through the steps to investigate it, I can't find the cause. Here's what I see whenever I start tomcat on CentOS servers running various applications:

May 1, 2014 8:50:29 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jv    m/java-1.6.0-openjdk-    6_64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
May 1, 2014 8:50:29 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
May 1, 2014 8:50:29 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1382 ms
May 1, 2014 8:50:29 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
May 1, 2014 8:50:29 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.24
May 1, 2014 8:50:29 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive ROOT.war
log4j:ERROR setFile(null,true) call failed. ../logs/dc.log (No such file or directory)
        at Method)
        at org.apache.log4j.FileAppender.setFile(
        at org.apache.log4j.RollingFileAppender.setFile(
        at org.apache.log4j.FileAppender.activateOptions(
        at org.apache.log4j.config.PropertySetter.activate(
        at org.apache.log4j.xml.DOMConfigurator.parseAppender(
        at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(
        at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(
        at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(
        at org.apache.log4j.xml.DOMConfigurator.parseCategory(
        at org.apache.log4j.xml.DOMConfigurator.parse(
        at org.apache.log4j.xml.DOMConfigurator.doConfigure(
        at org.apache.log4j.xml.DOMConfigurator.doConfigure(
        at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(
        at org.apache.log4j.LogManager.<clinit>(
        at org.apache.log4j.Logger.getLogger(
        at org.apache.commons.logging.impl.Log4JLogger.getLogger(
        at org.apache.commons.logging.impl.Log4JLogger.<init>(
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
        at java.lang.reflect.Constructor.newInstance(
        at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(
        at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(
        at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(
        at org.apache.commons.logging.LogFactory.getLog(
        at org.springframework.util.PropertyPlaceholderHelper.<clinit>(
        at org.springframework.util.SystemPropertyUtils.<clinit>(
        at org.springframework.util.Log4jConfigurer.initLogging(
        at org.springframework.web.util.Log4jWebConfigurer.initLogging(
        at org.springframework.web.util.Log4jConfigListener.contextInitialized(
        at org.apache.catalina.core.StandardContext.listenerStart(
        at org.apache.catalina.core.StandardContext.start(
        at org.apache.catalina.core.ContainerBase.addChildInternal(
        at org.apache.catalina.core.ContainerBase.addChild(
        at org.apache.catalina.core.StandardHost.addChild(
        at org.apache.catalina.startup.HostConfig.deployWAR(
        at org.apache.catalina.startup.HostConfig.deployWARs(
        at org.apache.catalina.startup.HostConfig.deployApps(
        at org.apache.catalina.startup.HostConfig.start(
        at org.apache.catalina.startup.HostConfig.lifecycleEvent(
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(
        at org.apache.catalina.core.ContainerBase.start(
        at org.apache.catalina.core.StandardHost.start(
        at org.apache.catalina.core.ContainerBase.start(
        at org.apache.catalina.core.StandardEngine.start(
        at org.apache.catalina.core.StandardService.start(
        at org.apache.catalina.core.StandardServer.start(
        at org.apache.catalina.startup.Catalina.start(
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.apache.catalina.startup.Bootstrap.start(
        at org.apache.catalina.startup.Bootstrap.main(

It never causes a problem, but I cannot find "dc.log" in any configuration file anywhere on the server, much less tomcat, so I don't know what is causing this error. Google searches have come back with no results which I find hard to believe. How can I hunt this down?

share|improve this question
up vote 1 down vote accepted

The hint is in the exception: log4j is complaining. Assuming that the configuration files you've checked were all in $TOMCAT_HOME/conf, you're going to need to dig in to the properties files deployed by ROOT.war.

grep -r dc.log webapps is the laziest way to get what you're looking for.

(In other words, blame your developers.)

share|improve this answer
My first thought is always to blame developers. :) I did a grep -R dc.log * in $TOMCAT_HOME and got no hits. That's what is confusing me. – DrStrangepork May 1 '14 at 22:43
It will be in there somewhere for sure. The next logical step is to assume that this filename is constructed by smashing strings you're going to have to deal with the spam of a search for .log or dc. :( – Andrew B May 1 '14 at 22:58
Found it. It was within one of the jar files in webapps/<WAR>/WEB-INF/lib, so grep wouldn't have found it. Needed zipgrep. So while in the webapps directory, this revealed the culprit: for i in ``find . -name "*.jar"``; do echo $i ; zipgrep "dc.log" $i; done. In the end, developer's fault. – DrStrangepork May 1 '14 at 23:10
There also seems to be no way to escape a backtick in a comment, so those double-backticks above were really just single backticks... – DrStrangepork May 1 '14 at 23:14
Nicely done. Glad you were able to find it, chasing those can be a real pain sometimes. – Andrew B May 1 '14 at 23:36

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.