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 Developers List" <dev@tomcat.apache.org> > Date: Wednesday, July 23, 2008, 4:26 PM > 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. > > Best regards, > -Felix > > > Fu-Tung Cheng wrote: > > Hi, > > > > I sometime hotdeploy my war file to tomcat 6.0.16. I > have noticed that a static variable in one of my classes > then ends up being null. > > > > The variable is initialized as follows: > > > > private static Logger logger = > Logger.getLogger(MyClass.class); > > > > and then used below in a method: > > > > public void mymethod(String mystring) { > > logger.info(mystring + " did something"); > > } > > > > This is a little annoying as I then need to restart > the server for this class to work properly. > > > > Is this a known bug? I could probably create a little > sample war file to demonstrate the issue but I don't > want to go through that if you guys already know about the > issue. > > > > Thanks, > > > > Fu-Tung > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
