Howdy, One comment/question: the killing thread will only be used by choice, i.e. someone explicitly setting the shutdownWait > 0. Accordingly, for that person the killing thread shutdown will be a normal shutdown, and the exit status should be zero instead of one, right?
Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Tim Funk [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, February 11, 2003 9:44 AM >To: Tomcat Developers List >Subject: [PATCH] Allow System.exit to be called on shutdown [was Re: >Shutdown.sh does not work when long lasting operations, such as SQL >Queries, are still active! > >Here is the patch to StandardServer.java and LocalStrings.properties. > >Synopsis: > New property: shutdownWait if greater than zero. Then to the end of >shutdown, a new daemon thread is created which sleeps for {shutdownWait} >seconds. When (and if) the Thread wakes back up, it prints to >System.out() then new message in LocalStrings.properties and then calls >System.exit. > >shutdownWait defaults to zero. If zero or neagtive, then it is ignored >and the old behavior occurs. (Which is to do nothing extra) > >This patch was from tomcat5. > >If this is good enough to accept, I can later submit the patches for the >admin app and mbeans-descriptors.xml. > >Also attached is the JSP I used to ensure the server stayed running. >Ignore the quality of the jsp - its just a test. > > >-Tim > > >Craig R. McClanahan wrote: >> >> On Mon, 10 Feb 2003, Tim Funk wrote: >> >> >>>Why is a kill done instead of a System.exit()? >> >> >> System.exit() is absolutely the wrong answer if Tomcat is embedded into a >> larger server-side application, rather than run separately in the usual >> way. At best, you would need to make this configurable somehow (with the >> default to *not* run System.exit()). >> >> Craig >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
