https://issues.apache.org/bugzilla/show_bug.cgi?id=46263
Summary: Tomcat reloading of context does not update context path
Product: Tomcat 6
Version: 6.0.18
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: Catalina
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
Tomcat reloading of context does not update context path
Several years ago I worked on integrating tomcat 5.5 into our web application
management infrastructure. During the process I fixed several tomcat 5.5 bugs,
but apparently never sent the fixes upstream. Oops.
Our application environment requires that we be able to upgrade to a newer
version of code for our application without loosing any webrequests. One major
obstacle was fixed with Bug #43683. Another obstacle is the changing of the
docBase of the context itself during the reload.
If you are running in autoDeploy="false" mode, and you start a context (EG:
visit the url of one of the servlets), if you update the docBase in the context
xml file on disk, and then reload that context using the tomcat-hostmanager
app:
w3m http://localhost:8180/tomcat-manager/reload?path=/thecontext
The context will reload, however the new docBase will not be respected. It
will reload the original docBase.
If you tomcat-manager/stop then tomcat-manager/start, your updates will be
respected, but the transfer to the new docBase is not atomic (you will loose
requests).
If you run in autoDeploy="true" mode, the new docBase will be respected,
however the transfer to the new docBase is not atomic (you will loose
requests).
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
