DO NOT REPLY [Bug 11754] New: - Synchronous shutdown script - shutdown.sh should wait until Tomcat is fully shut down

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11754>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11754

Synchronous shutdown script - shutdown.sh should wait until Tomcat is fully shut down

           Summary: Synchronous shutdown script - shutdown.sh should wait
                    until Tomcat is fully shut down
           Product: Tomcat 4
           Version: 4.0.4 Final
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: alex@apache.org


Currently the shutdown script ("shutdown.sh" or "catalina.sh
shutdown") connects to Tomcat, tells it to shut down, then immediately
exits.  It would be desirable if there were a mode in which it delayed
exiting until all webapps were completely shut down and no aspect of
the server were able to accept TCP or HTTP requests.

Bonus points if it provided feedback during the shutdown process,
announcing mesages like "Beginning to stop context foo" and "Finished
stopping context foo" and "Tomcat completely shut down".

Motivation: I have been using Tomcat in a testing mode, where I launch
Tomcat, run my tests, and then shut Tomcat down.  Prior to launching
Tomcat, I need to shut down any *already-running* instances.  However,
since the time required to *really* shut down is variable, I often
misjudge the timing and end up launching the new instance before the
old one is shut down.  This leads to an unclean startup for the new
instance, due to (I presume) port conflicts.  If, instead, the
shutdown script did not exit until shutdown of the old instance were
*complete* (and not just started), I would be assured of a clean
startup for the new instance.

A simple implementation of this would just "ping" the control port,
exiting only when the port is closed.  Would that work, or is it
possible that the control port is closed (no longer accepting
requests) but one or more contexts are still active?

I have been off the Tomcat team for a while, but if this feature is
desirable, and a current developer wants to point me in the right
direction, please let me know and I'll see if I can take a stab at
writing a patch myself.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>