Bug 36990 - Undeployment fails when Tomcat service is restarted after successful deployment
Summary: Undeployment fails when Tomcat service is restarted after successful deployment
Status: RESOLVED WONTFIX
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Webapps:Manager (show other bugs)
Version: 5.5.9
Hardware: Other Windows 2000
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-10 15:44 UTC by Allistair Crossley
Modified: 2005-10-16 22:02 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Allistair Crossley 2005-10-10 15:44:12 UTC 
This may not be a bug as such, but I do not believe it is correct behaviour. It 
is using the Ant deploy script for a target Tomcat 5.5.12 for Windows using the 
service.

1. Deploy a WAR to a clean Tomcat using an embedded META-INF/context.xml, 
path="ROOT"
2. Application is deployed OK, requests succeed OK.
3. Restart Tomcat service
4. Call undeploy of ROOT web application

The undeploy fails with FAIL - No context exists for path /ROOT despite the 
following 3 facts

1. /conf/Catalina/localhost/ROOT.xml exists
2. /webapps/ROOT.war exists
3. /webapps/ROOT (exploded) exists

Is it correct that a restart of Tomcat should prevent undeployments of 
previously deployed webapps?
Comment 1 Yoav Shapira 2005-10-17 06:02:13 UTC 
No, it's not correct, but the ROOT path is a special case, to be avoided.