DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=41939>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41939 ------- Additional Comments From [EMAIL PROTECTED] 2007-04-19 16:49 ------- I am hunting for permgen leaks as the moment and have wildly inconsistent results with context reloading. Most of the time the first loaded webapp will not garbage but some subsequent reloads are grabaged. The Tomcat FAQ section should have it spelled out under a title called 'Log4J' the best way to include log4j and the implications of having the commons-logging. Currently the 'How should I log in my own webapps?' section 'strongly recommends' using log4j but does not address any of these issues. There are many different approaches listed on the web some of which go as far as replacing the bootstrap logging. e.g. /commons/lib/commons-logging.jar /commons/lib/log4j.jar /commons/classes/log4j.properties /<APP>/WEB-INF/lib/log4j.jar /<APP>/WEB-INF/lib/commons-logging.jar /<APP>/WEB-INF/classes/log4j.properties It should spell out things like the following: If you have commons-logging.jar in your webapp then it will not garbage. If you don't have log4j.jar in your webapp then you will not get per-content logging of you /<APP>/classes/log4j.properties file Kind regards James McIntosh -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
