2012/6/28 Neena Damodaran <neena.damoda...@db.com>: > Classification: For internal use only
If it is "for internal use", do not post it to a publicly archived mailing list. The same for your "disclaimer" below. > > We have issues with logging with one of our customers in production. > We have log4J configured in our application. > But for this one customer the logs that are written to Application.log is > also > going to STDOUT.log and because of this STDOUT.log is growing very huge > and the > customer has to restart the server daily. > Configure your logging framework and all other logging frameworks used in your configuration to do not log anything to the console/stderr/stdout. Tomcat internal logging uses java.util.logging by default. You would look for java.util.logging.ConsoleHandler. There is similar class in Log4J. You usually need to see the actual log messages to decide what component wrote them. > This is happening with only one customer who is using our product and we > are not > able to replicate it. I don think log4J is a problem because then it would > have occured at > every customer's environment. > > I could remove the STDOUT.log by removing the PR_STDOUT property from the > registry > but I don want to do this. It is unlikely that it will help. > Could you provide a solution for this. > > The tomcat version that is being used is Apache Tomcat Version 6.0.13 Which has known security issues. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
