Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 4562 invoked from network); 16 Aug 2003 04:07:29 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 16 Aug 2003 04:07:29 -0000 Received: (qmail 14167 invoked by uid 50); 16 Aug 2003 04:10:21 -0000 Date: 16 Aug 2003 04:10:21 -0000 Message-ID: <20030816041021.14166.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 22478] New: - Ant manager deploy causing webapp to initialize twice X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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 Summary: Ant manager deploy causing webapp to initialize twice Product: Tomcat 5 Version: 5.0.7 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Webapps:Administration AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: hoju@visi.com If have my webapp sitting in CATALINA_HOME/webapps and my context configuration file in conf/Catalina/localhost before Tomcat starts, initialization is done once. If, however, I do a deploy using the Ant manager deploy task, initialization is performed twice. Actually, this happens more clearly after an Ant manager deploy + html manager undeploy + Ant manager deploy. The first time it is deployed, I get an exception from digester which seems to prevent the duplicate initialization. I'll be attaching text file showing the log output from stdout.log (I run Tomcat as a WinXP service) and localhost_log that shows the stack traces. Like I said, it is more clear the duplicate initialization is happening after a deploy + undeploy + deploy. Here is what it looks like beginning with the undeploy... 3124297 [http8080-Processor25] INFO org.apache.catalina.core.ContainerBase - Removing web application at context path /Barracuda 3125031 [http8080-Processor25] INFO org.apache.catalina.logger.LoggerBase - unregistering logger Catalina:type=Logger,path=/Barracuda,host=localhost 3192547 [http8080-Processor24] INFO org.apache.catalina.core.StandardHostDeployer - Installing web application from Config file URL file:/D:/Java/Apache/Jakarta/tomcat-5.0.7/conf/Catalina/localhost/Barracuda.xml 3192547 [http8080-Processor24] INFO org.apache.catalina.core.StandardHostDeployer - Installing web application from URL jar:file:/D:/Java/Apache/Jakarta/tomcat-5.0.7/webapps/Barracuda.war!/ Aug 15, 2003 8:33:25 PM org.apache.catalina.loader.WebappClassLoader findResourceInternal INFO: Lifecycle error : CL stopped java.lang.IncompatibleClassChangeError: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1251) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1211) at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:93) at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:174) at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:93) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:644) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:616) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:584) at org.apache.log4j.xml.XMLWatchdog.doOnChange(DOMConfigurator.java:815) at org.apache.log4j.helpers.FileWatchdog.checkAndConfigure(FileWatchdog.java:80) at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:99) Aug 15, 2003 8:33:26 PM org.apache.catalina.loader.WebappClassLoader findResourceInternal INFO: Lifecycle error : CL stopped java.lang.IncompatibleClassChangeError: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1251) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1211) at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:93) at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:174) at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:93) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:644) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:616) at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:584) at org.apache.log4j.xml.XMLWatchdog.doOnChange(DOMConfigurator.java:815) at org.apache.log4j.helpers.FileWatchdog.checkAndConfigure(FileWatchdog.java:80) at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:99) [webapp specific initialization logging happens here.....] 3216172 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] INFO org.apache.catalina.startup.HostConfig - restartContext(/Barracuda) 3216672 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] INFO org.apache.catalina.logger.LoggerBase - unregistering logger Catalina:type=Logger,path=/Barracuda,host=localhost [webapp specific initialization logging happens...again...here.....] Note that after this happens, the webapp actually works fine. It most certainly shouldn't be initializing twice, though. I won't speculate as to the cause. I'll wait for some more inciteful interpretation from Remy, Bill Barker, or someone else more attuned to the workings of the Tomcat internals. Jake