You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/08/16 01:38:00 UTC
DO NOT REPLY [Bug 11753] New: -
Synchronous startup script - startup.sh should wait until Tomcat is fully started
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=11753>.
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=11753
Synchronous startup script - startup.sh should wait until Tomcat is fully started
Summary: Synchronous startup script - startup.sh should wait
until Tomcat is fully started
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 startup script ("startup.sh" or "catalina.sh startup")
launches Tomcat in a background process, then immediately exits. It
would be desirable if there were a mode in which it delayed exiting
until all webapps were initialized, running, and able to accept HTTP
requests.
Bonus points if it provided feedback during the startup process,
announcing log mesages like "Starting context foo" back to the caller
until all contexts are ready.
Even more bonus points if it prints an error and returns a nonzero
exit status if the server could not start for some reason.
(e.g. "java.net.BindException: Address already in use:8080" or
"StandardServer.await: create[8005]: java.net.BindException: Address
already in use", both of which mean that a prior instance of Tomcat
has not been 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. If the tests
immediately start sending requests to Tomcat, I often get errors
(which I will summarize in a separate bug report) that are due to the
webapp or server not being completely started up. A workaround is to
use a delay between Tomcat startup and running the tests.
Unfortunately, the amount of time necessary for the delay is variable
(from 10 to 45 seconds depending on load and CPU speed), and since I
run these tests frequently, every second counts.
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>