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

Out Tomcat 8 is logging so much so that by the evening the catalina.out inflates to GBs of data. I followed the procedure given on the tomcat website to replace JULI logging with LOG4J. Now LOG4J has started logging in catalina but catalina.out is still being logged in as earlier. We are using Java 7 over Redhat 5. I have also commented everything out in the JRE logging properties file as well. Please advise.

share|improve this question
LOG4J vs JULI logging has nothing to do with your issue. The only reason to switch logging framework in this case would be if you cannot figure out how to configure JULI logging as opposed to configuring LOG4J ... but that would be treating the symptom and not he cause. – unixhacker2010 Jan 26 '14 at 12:33

You need to change in conf/ the property org.apache.catalina.level to log level you want to have.

share|improve this answer
That was not affecting the size of the logs. Than, to switch to log4j from juli, I followed the instructions on the Tomcat website and deleted the conf/ file altogether. But the logging still hasn't stopped. – 6nagi9 Jan 14 '14 at 3:46
@6nagi9: It's not the JRE's you need to change, it is that of Tomcat which you'll find in the $CATALINA_BASE/conf/, alternatively one of the webapps on that Tomcat may have its own logging properties and in that case it will (typically) be in .../webapps/<appname>/WEB-INF/classes/ file. – unixhacker2010 Jan 26 '14 at 12:31
there isn't any webapps logging properties file and i have commented out both catalina as well as jre logging properties files. – 6nagi9 Jan 27 '14 at 13:41

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.