Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" for change notification.
The following page has been changed by CekiGulcu: http://wiki.apache.org/jakarta-commons/Logging/UndeployMemoryLeak ------------------------------------------------------------------------------ model by keeping component libs inside the component will mean this problem never occurs. + == Comment's by Ceki Gulcu == + + Simon, I've enjoyed reading your article. Cognizant of the memory leak + problem you mention, the version of log4j which is currently CVS HEAD, + does "not" include a context selector based on class loaders. The only + selector which is included is based on JNDI. Unless I am missing + something, ContextJNDISelector does not cause memory leaks. Previous + versions of log4j (e.g. 1.2) did not ship with any selectors. + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
