tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35308] - Create a graceful restart mechanism like an Apache-http-server
Date Fri, 10 Jun 2005 21:56:15 GMT
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=35308>.
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=35308


bht@actrix.gen.nz changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bht@actrix.gen.nz




------- Additional Comments From bht@actrix.gen.nz  2005-06-10 23:56 -------
Please also also refer to bug 34140.

I was (probably incorrectly) assuming that the Tomcat implementation of the
stop() method in the org.apache.commons.daemon.Daemon interface blocks until all
requests are serviced and no new requests are admitted.

If what Remy Maucherat says is correct that Tomcat only waits a little then this
is not sufficient as one cannot possibly know how long a request takes to
complete unless on can watch pending requests.

I am kindly asking for confirmation that Tomcat truly waits for the last pending
request to terminate and then immediately returns from stop(). If that question
cannot be answered with "yes" then re-opening of this bug should be considered.

Another thought which is probaly close to what the reporter has in mind is a
reload function that avoids re-instantiating the server but re-loads
configuration files, i.e. calls stop(), init() and start() in that sequence. I
guess this would have to be implemented through BOTH the socket control
interface and the commons-daemon project. This also be useful for those who run
httpd mod_jk with the only difference that they have to use an extended
sequence: httpd stop, tomcat reload, httpd start. Obviously they they have to
stop httpd entirely because otherwise server errors would occur while httpd is
running and cannot connect to the reloading tomcat.

-- 
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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message