On 09/03/2011 15:06, Jess Holle wrote: > So there's no way to do this from the Tomcat side? > > The process embedding Tomcat knows it's stopping. It does not > necessarily even have an ability to connect to the web server(s) that > are connecting to it [Apache, IIS, or SJWS, but all via the JK > connector]. I therefore want to say "this Tomcat no longer open for > business" from the Tomcat side while finishing all requests already in > progress. > > Also I was somewhat inaccurate/mistaken in my summary of Tomcat 7.0.10 > behavior. If you invoke stop() and then destroy() on a connector(), > then an exception is logged /but /the destroy() call succeeds. That > said, when it succeeds you get a 200 with no content on the next > request. The request *after* that is returns a 503 from Apache -- and > presumably would have been load balanced to another Tomcat (I only have > 1 in my test at the moment). There's still odd behavior for a single > request after the stop/destroy().
Can you post the Exception? That sounds like a bug that needs to be fixed. I recall coming across this before. I think it was related to keep-alive connections and was non-trivial to solve. Open a bugzilla entry and I'll take another look. No promises though. It might end up as won't fix. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
