Have some functionality in your app to block any more logins so that only existing users can finish their work. When the requests to ur Webapp die you can first block ALL access to your app and then shutdown tomcat first and Apache after it.
This is how i had implemented the functionality in an application. Affan ----- Original Message ----- From: "Christoph Fischer" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Wednesday, March 12, 2003 8:31 PM Subject: Re: Shutdown sequence of Apache and Tomcat > I don't know if there is a graceful way to exit. > If you stop tomcat first, users will get an error-Message that tomcat is > not available, > on the other side if you stop apache first, results from tomcat may > leave an uncomplete page > for the user. Personally I prefer apache and then tomcat shutoff. > chris > > Raja Sekhar wrote: > > >Hi, > > > >I am using Apache Webserver 1.3.27 and Tomcat 4.0.6 with AJP 1.3 connector configured on Linux server. Can any say me what should be the sequence of shutdown of these servers... > > > >I mean whether Apache should start first or tomcat and even when shutting down what should be the sequence? Can any one give me some URL which explains this... > > > >Our sysadmin guys want this.. So please help me out.. > > > >Regards, > > > >..Raj > > > > > > > >Need a new email address that people can remember > >Check out the new EudoraMail at > >http://www.eudoramail.com > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
