Yeah, I'm removing the machines from the load balancer to prevent new connections, but was curious for existing connections including those being kept around due to keep alive.
We are using using the JSVC stop action, so I guess pulling the machine from the load balancer, watching opened connections until long running / keep alive are left, and stopping Tomcat is the best thing to do outside of waiting for the connections to close themselves. On Oct 13, 2012, at 4:39 AM, Mark Thomas <ma...@apache.org> wrote: > On 13/10/2012 04:27, Andrew Feller wrote: >> Is there a graceful way to drain connections and shutdown Tomcat with JSVC? > > Not JSVC specific but if you pause a connector (e.g. via JMX) all > current requests will be allowed to complete but no new requests > (including those over keep-alive connections) will be permitted. > > Then you can issue a connector stop which will close any still open > connections. > > Stopping a connector will close all current connections even if requests > are in progress. > >> I've been unsuccessful finding anything documented about this, so I >> imagine people have a variety of non-standard ways or don't care. > > Folks normally do this behind a load-balancer and that takes care of > draining the connections. > > Mark > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
