let me know if I read that right...
Bill Barker wrote:
When you have the log4j jar in WEB-INF/lib, the it ends up being used by Tomcat for some of it's logging. As a result, it can cause memory leaks and
other weird errors when a context is stopped and started. This isn't a
problem with j.u.l since the classes are loaded by the system classloader.
That is why Tomcat decided to use j.u.l for it's internal logging by
default.
does this mean that including log4j in my deployment WAR could
potentially cause memory leaks and problems with tomcat? I've never
heard of this, I thought that log4j played well with others, has anyone
else experienced this / are there any links that describe this problem/
cheers.
--
Matthew Kerle
IT Consultant
Canberra, Australia
Mobile: +61404 096 863
Email : [EMAIL PROTECTED]
Web : http://threebrightlights.blogspot.com/
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
