DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22478>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22478 Ant manager deploy causing webapp to initialize twice ------- Additional Comments From [EMAIL PROTECTED] 2003-08-18 03:21 ------- Remy, I've tested your fix and it seems to have solved the duplicate initialization. I will look into how it is that Log4j seems to be accessing a stopped class classloader even when I call LogManager.shutdown() in the contextDestroyed() method of my servlet context listener. Maybe shutdown() is not doing everything it should be doing? Anyway, I'll look into it. I am still seeing the Digester error upon initial deploy. Here is how it looks now.. 82437 [http8080-Processor25] INFO org.apache.catalina.core.StandardHostDeployer - Processing Context configuration file URL file:/D:/Java/Apache/Jakarta/tomcat-5-20030817/conf/Catalina/localhost/Barracuda.xml 82437 [http8080-Processor25] INFO org.apache.catalina.core.StandardHostDeployer - Installing web application from URL jar:file:/D:/Java/Apache/Jakarta/tomcat-5-20030817/webapps/Barracuda.war!/ 104078 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] INFO org.apache.catalina.core.StandardHostDeployer - Processing Context configuration file URL file:D:\Java\Apache\Jakarta\tomcat-5-20030817\conf\Catalina\localhost\Barracuda.xml 104093 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] ERROR org.apache.commons.digester.Digester - End event threw exception Notice how Tomcat processes the context configuration file after the context has already been installed? I also see the following in the log for my particular webapp after an undeploy, then deploy... 2003-08-17 17:48:50 createObjectName with StandardEngine[Catalina].StandardHost[localhost].StandardContext[/Barracuda] 2003-08-17 17:50:35 createObjectName with StandardEngine[Catalina].StandardHost[localhost].StandardContext[/Barracuda] The first line was logged at the end of an undeploy and the second at the beginning of a deploy. It seems fishy to me that it would do a "createObjectName" after an undeploy when the very same thing is done again upon a deploy. I don't know if this is significant or not. If it isn't, just say so. Jake --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
