commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gulcu <c...@qos.ch>
Subject Re: Fwd: commons-logging unsuited for cross-context webapplication invocation usage - migrating to slf4j?
Date Fri, 24 Apr 2009 09:54:30 GMT


Mark Thomas wrote:
> 
> Two web applications both using slf4j with java.util.logging and both
> using a third party library that has a logger called "MyLogger".
> 
> When web app one uses the library, slf4j will return - via a call to
> j.u.l.getLogger() - a new logger called MyLogger. When web app two uses
> the library it will get the same logger instance as web app one. This
> type of behaviour is often at the root of permgen memory leaks.

Where is the 3rd party library located on the class path? Is the 3rd party 
library loaded by a shared/common class loader, parent of the web-app class loaders?

-- 
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message