Joleen, On 11/30/15 11:44 AM, Joleen Barker wrote: > OMG!!! Finally. I feel like I can go back to the bosses with some progress. > This is all good news. Also, thanks for the correction on the "lo and > behold", I never knew that. I have to laugh at myself.
Sometimes, this list can be more of a grammar and etiquette support group than anything else. Glad I could help. > I can change the catalina file name to the name catalina.log, I think you > are right and it be less confusing. > > Yes, nothing is going to catalina.out anymore. > > In the production environment there is almost always activity so then the > new catalina.log file will be rollover pretty close to midnight every day. It should. As many issues are not reproducible in dev/test that plague production, at the very least production gets much more activity, so this issue shouldn't come up too often. You could even write a script to ping your server once every hour on the :01 to trip the log file if you were very worried about it. > Now I'm really excited about implementing these changes in our big test > environment that has a lot of activity. My little system at home is not > used as much so I didn't get to experience the rollover. But I learned a > lot from this experience. > > I will want to build from this setup to attempting to control what data is > written where as right now there is a lot of duplicate information going to > both the catalina and localhost file but I think it would be a separate > email stream. Right. For this, you'll want to look at setting the configuration for each web application, like this: log4j.logger.org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/your-web-app]=INFO, SOME_NEW_APPENDER This will keep it from going to the CATALINA appender, which is the default logger in the most-recent configuration you posted to the list. Good luck, -chris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
