Our tomcat administrator has left us not too long ago, and now I'm tasked with maintaining the 5.5.17 tomcat server.
The output of the tomcat log, as specified in the log4j.properties file, is stopping at a certain point in the morning. The application runs continuously throughout the day and the output has always been steady. This started two weeks ago and I'm baffled.
It's not hurting the application as it runs fine. It's just that I rely on the log for debugging and testing.
Any advice you can give me is greatly appreciated.
Bill Clar [ October 04, 2007: Message edited by: Bill Clar ]
With log4j, it's possible to change your logging levels at run time from within your program.
I'm wondering if someone wrote something that turns the logging levels up a 4:00 AM to debug some type of batch process and then, with the best of intentions, set it to turn the logging off when this process is done.
Do you know of any code in your application that does something automatically every morning?
I'm afraid that we don't utilize the log4j to our fullest advantage in that we don't utilize the debugging levels. All of our output comes from System.out.println(). It's not the best approach, but we have little time for refactoring at the moment.
All automated processes run at night, after hours. The output from those processes are piped to the default log of catalina.out without any problem.
I appreciate your help, Ben.
I'm going to consult with my system administrator and see if it could be a disk space or memory issue. Upgrading our version of Tomcat is another option.