tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 46263] Tomcat reloading of context.xml does not update docBase
Date Wed, 13 Nov 2013 01:07:12 GMT

Joe Kislo <> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |---

--- Comment #6 from Joe Kislo <> ---
To answer Christopher Schultz:
  We are try to upgrade a web application from one build to a newer build, so
we would want to use the same URL, but with the newer version of the
application, and we do not want to loose any requests when the transition is
happening.  So we can't undeploy and redeploy.

To answer Mark Thomas:
  We looked into the parallel code deployment feature of Tomcat 7, and it is a
very clever way to solve this issue.  I suspect it will be sufficient for most
people.  However in our case we do need fine-grained control of the starting
and stopping of a specific version of the application.  We handle long-running
requests in a special manner in the servlet destroy() and we know the new code
is not deployed prior to them being serviced or 'dealt with'.  We also
synchronize code upgrades with other non-servlet deployments of the code base,
so having 'old' or 'unknown' versions of the servlet running out there is not
something that works for us.  Our deployment mechanism communicates with a
number of different components, tomcat being just one, and knowing the specific
state of each server is important.

I am reopening this bug/feature request, because I believe it is beneficial for
tomcat to have this capability, and it is a capability present in the
application server we migrated from (and I suspect is a common capability in
other application servers).  I am attaching an updated patch that applies to
Tomcat 7.0.42.  

Mark, if your opinion Tomcat is better without this capability, feel free to
re-close as wontfix and I won't be offended.  :)

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message