On 08/05/2012 21:33, Mladen Turk wrote: > On 05/08/2012 08:54 PM, Mark Thomas wrote: >> On 08/05/2012 19:47, Costin Manolache wrote: >>> You may still want to accept requests for existing sessions. >>> >>> Both 'graceful shutdown' and app deploy are important cases - it's just >>> that current 'pause()' is not that good for either of them, if you >>> really >>> want to cleanup... >>> >>> Maybe an option to return 503 or custom status/headers - so people can >>> adjust to various LBs. >> >> pause() on the connector means something very different to pause in the >> reverse proxy. In the connector pause means: >> - stop processing new connections >> - close existing connections > > So it closes existing connections or waits for response finish > and closes the sockets?
If the request line has been processed, a request is allowed to complete and then the connection is closed. If a connection is in keep-alive, the connection is closed immediately. Mark > I always thought it's similar to graceful shutdown which > would imply that it waits till all current req/resp > cycles are finished (probably forcing keepAlive = false) > >> - keep the socket bound >> >> It is very similar to stop() if bindOnInit==true >> > > > > > > Regards --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
