Re: hotdeploy of war files results in static variable being null

Hi Felix, Thank you for the link. Quite informative!!! Fu-Tung --- On Wed, 7/23/08, Felix Gnass <[EMAIL PROTECTED]> wrote: > From: Felix Gnass <[EMAIL PROTECTED]> > Subject: Re: hotdeploy of war files results in static variable being null > To: "Tomcat Developer

Re: hotdeploy of war files results in static variable being null

Talking about loggers and NullPointerExceptions ... I get the following stacktrace every time an application is re-deployed: log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository. Jul 23, 2008 4:31:47 PM org.apache.catalina.core.St

Re: hotdeploy of war files results in static variable being null

Hi, as far as I know Tomcat's WebappClassloader sets final static references to null upon re-deployments to prevent memory leaks. The following page describes what's happening: http://wiki.apache.org/jakarta-commons/Logging/StaticLog One possible solution would be not to use static loggers.