DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40347>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40347 Summary: Manager displays spurious contexts when multi-level context paths are used Product: Tomcat 5 Version: 5.5.17 Platform: All OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Webapps:Manager AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] We deploy Web applications using three-level context paths like "/webinfra/access/webapp". When an app is deployed this way in Tomcat 5.5 using a Context XML file, spurious "applications" are created that then appear in the app list displayed by the Manager. In the case mentioned here (for example), "/webinfra" appears in the list once the real application has been deployed. The spurious application can be undeployed from the Manager, and that effectively undeploys the original as well. This is operationally troublesome and confusing, and it differs from the behavior in Tomcat 5.0 (from which we want to convert). Note that the spurious contexts only appear if "unpackWARs" is set to "true" (the default) so that WAR files are expanded into Tomcat's work area. (Running with "unpackWARs" set to "false" is no longer a viable option for us because, in that configuration, changes to the underlying WAR files, which we can't reliably prevent, often lead to JVM crashes on a running system.) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
