Since nobody answered on tomcat-user, I'll just forward this one here (since I think it actually belongs here in the first place..)
---------- Forwarded message ---------- Date: Tue, 20 Nov 2001 18:14:20 +0100 (MET) From: Endre Stølsvik <[EMAIL PROTECTED]> Reply-To: Tomcat Users List <[EMAIL PROTECTED]> To: Tomcat user list <[EMAIL PROTECTED]> Subject: [TC4] How to know when tomcat is properly shut down? The catalina.sh and related scripts all start the Bootstrap.java class and asks it to shut down Catalina. This script, if successful in connecting to the shutdown port of Catalina, returns immediately. This whether or not there is 8953289527 pending database commits or whatever that has to be done before things actually are properly shut down. This is highly undesirable, and I would love if it were possible to shut down catalina and then chill untill it actually has shut down. This is especially important when shutting down the entire server, as the database shutdown might be the next in line, in which case everything breaks.. Of course, it would also be very nice if one could know if Catalina has properly come up. It could for example write a "boolean file" when the server has initialized all webapps, and then delete the same file right before the main method of Catalina exits on shutdown. Or one could use Bootstrap with argument -waitForUp or something.. --------------- And yes, Henri's init.d scripts also just fake this, waiting in just 2 seconds, which is too short time, and therefore the "restart" option of the init.d script is flawed. The shutdown part of it doesn't wait at all, so you might end up shutting the server physically down (read as: killing all the java threads w/o cleaning up) before tomcat has finished shutting down. Mvh, Endre -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
