2016-03-11 2:49 GMT+03:00 Joleen Barker <oldenuf2no...@gmail.com>: > I wanted to let you know that I really tried at this and feel the changes I > made should be working and it is a matter of the developer hard coding the > log messages to go to the stdout/stderr and became lazy as one of the other > that commented had stated. I opened a ticket with the vendor but I have no > idea how long it will take. So I went the route of writing a small perl > script to copy the catalina.out file to a file with the same name and the > date and time appended on the file name and then next I open the existing > catalina.out file to clear the contents and then close it again to start > the next day with a clean log file. It isn't the way I wanted to go but I > ran out of time. If the vendor decides to work with me, it would be great > but I have a feeling they will not go back and change things. >
On the logging page of the FAQ: https://wiki.apache.org/tomcat/FAQ/Logging#Q10 By the way, 1) It is possible to run with a debugger and put a breakpoint into java.io.PrintStream.println(String). I doubt that the PrintStream class is used much anywhere except to implement System.out/System.err. https://wiki.apache.org/tomcat/FAQ/Developing#Debugging 2) It is possible to search the class files for the message text. The classes store it in UTF-8, and jar files are just zip archives. > So are you suggesting to remove the ConsoleAppender from the > log4j.properties that the vendor has in the WEB-INF/classes directory? Yes. The same for Tomcat own log configuration, http://tomcat.apache.org/tomcat-8.0-doc/logging.html#Considerations_for_production_usage (Just mentioning for completeness. IIRC you have already reconfigured Tomcat own logging.) Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
