Ok.... another guess and another war story ;)
I found that if I did a URLConnection in a filter init.... I managed to
completely lock up Tomcat on a start.... stone dead...
I then deleted the War and the folder and after figuring out wot the problem
was, it would still not deploy the new one and start... only if I deleted
the conf/Catalina/host/(web-app).xml file did it recover.
So please try this as well... if there is a conf/Catalina/host/(web-app).xml
with the same name as you want to deploy... kill that as well.
ROOT.war is a little special... so wot I'm suggesting is you make sure that
you destroy any traces of a previous version in (conf and web-apps).
I've being trying to replicate wots happening to you and I cant... so sorry
run out of other ideas... but just to recap my weird experiences...
-- Netbeans can hang onto Tomcat...
-- A filter can cripple tomcat...
-- And the common factor seems to be if the context path under
conf/Catalina/host/webAppName.xml is still pointing at something else...
like the netbeans build... it sometimes ignores the WAR....
good Luck....
----- Original Message -----
From: "Michael Heinrichs" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Wednesday, May 09, 2007 7:36 PM
Subject: RE: WAR deployment incomplete (sometimes)
I don't see a consistent pattern, but it definitely happens on first
deployment. In my scenario, Tomcat is installed as part of a larger
product installation, with the WAR file under the webapps directory,
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
