https://bz.apache.org/bugzilla/show_bug.cgi?id=64080
--- Comment #7 from Mark Thomas <ma...@apache.org> --- I recommend folks take a look at bug 62515 and the associated commits before commenting further on this bug. It might save us all some time discussing what is and is not possible and what Tomcat currently does. Historically, the Tomcat approach has been to shut the server down ASAP, providing a 503 response or similar (e.g. a timeout signal for async) where the opportunity allows and allowing the request to complete (with a short timeout) where there is no opportunity for a 503. The move to non-blocking opened a gap where it is now possible that an in-flight request will just see a closed connection. Fixing the closed connection issue is relatively simple. Switching strategy from 'provide a 503 as early as possible' to 'allow requests to complete if possible' is a more invasive change and is not consistent with, historically, the behaviour Tomcat users have asked for on shutdown. Whether it is possible to make the shutdown strategy configurable isn't something I've looked at. That looks to be worth doing to see how invasive the patch to do that would be. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
