Ceki, Thanks for your response; I've done some more digging and discovered the following behavior.
As I said before when I first start jrun, everything is perfectly fine; if I touch then my servlet class, causing Jrun to dynamically destroy it and reload it, this causes log4j to report the following: log4j:ERROR A "org.apache.log4j.DailyRollingFileAppender" object is not assignable to a "org.apache.log4j.Appender" variable. log4j:ERROR Could not instantiate appender named "A1". log4j:ERROR A "org.apache.log4j.net.SMTPAppender" object is not assignable to a "org.apache.log4j.Appender" variable. log4j:ERROR Could not instantiate appender named "ML". log4j:WARN No appenders could be found for logger (HelloSso2Servlet). log4j:WARN Please initialize the log4j system properly. I indicated this before. Now, perhaps you can explain the following: If I then programmatically cause the servlet to call its own init() method later, after it has already been instantiated (when log4j failed to initialize), then everything returns to normal and log4j correctly initializes. Why does that happen? It's as if log4j cannot initialize when jrun first dynamically reloads the servlet-- but later, after the servlet has been instantiated, the PropertyConfigurator is successful. Is there some sort of race condition? How can I get around this? Thanks again, Whit _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
