Bug 58723 - Undeploy Versioned Context Fails
Undeploy Versioned Context Fails
Status: RESOLVED FIXED
Product: Tomcat 8
Classification: Unclassified
Component: Manager
8.0.27
All Linux
: P2 minor (vote)
: ----
Assigned To: Tomcat Developers Mailing List
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2015-12-11 19:12 UTC by Ben
Modified: 2015-12-18 15:47 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben 2015-12-11 19:12:51 UTC
With parallel deployment enabled and /context##version deployed, using http://localhost:8080/manager/text/undeploy?path=/context returns "FAIL - No context exists for path /context" but using /context##version is successful. Meanwhile, the context shown by /manager/text/list is /context, not /context##version:

/context:running:0:context##version

This is either a clarity issue in the documentation regarding the meaning of the term "context" ( http://tomcat.apache.org/tomcat-8.0-doc/manager-howto.html#List_Currently_Deployed_Applications ) or a behavior issue in the manager regarding the matching of the context string.
Comment 1 Mark Thomas 2015-12-18 15:47:13 UTC
It is mainly a documentation with the odd change required to error messages.

The manager app will use the context name or base file name when referring to a context so the message is unambiguous. In the past the path was used and I found one error message still using path rather than name.

The documentation wasn't fully updated when parallel deployment was introduced. The short version is whenever the docs say "path" read "path and optional version" with the version being required if you want to refer to a web application that has been deployed with a version.

I've updated the docs and error messages. The fixes will be in 9.0.0.M2 onwards, 8.0.31 onwards and 7.0.68 onwards. 6.0.x does not support parallel deployment.

[1] http://tomcat.apache.org/tomcat-9.0-doc/config/context.html#Naming