Hello all, We seem to be having the same problem as discussed in this thread: http://marc.info/?l=tomcat-user&m=117872182913850&w=2
The problem being that Tomcat on rare occasions does not completely unpack a war file. Our install procedure is very cut and dry: 1) stop/kill any running Tomcat processes 2) delete the old installation "rm -rf" 3) re-install Tomcat 4) install multiple war files into the 'webapps' dir. 5) install other pieces of the application into other non-Tomcat dirs. 6) start Tomcat 99...% of the time Tomcat starts up without a hitch. But every once in a great while, not sure how often, Tomcat will simply fail to deploy the entire contents of the war. I've only witnessed it 3 times (QA states it's happened more times). It's happened on 2 different webapps, and the 1 this happened to twice had different resulting exploded dirs. That is, they didn't stop deploying in the same spot. One time it stopped about 50% through and the other time about 95% of the way through. When this happens there are no startup errors. Tomcat starts up and the log indicates all wars were successfully deployed. One doesn't know there's been a failure until you hit the servlet and get a ClassNotFoundException. One time the log4j properties failed to be deployed so there wasn't even a log indicating a CNFE. Just as the previous post states, to get the system working one has to: stop Tomcat, delete the exploded dir, then restart Tomcat. Has anyone else ever seen this? Does anyone have any ideas as to why this may be happening? Any solutions, other than manually pre-explode the war files? Env: Solaris, jdk 1.5, Tomcat 6.0.14, war built via maven 2.0.9 Thanks, O --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
