https://bz.apache.org/bugzilla/show_bug.cgi?id=64080
--- Comment #2 from carbatt...@hotmail.com --- >Are you expecting Tomcat to process these requests normally (within some >>configured timeout or set of timeouts for each stage) or is cleanly returning >a >503 an acceptable response? In a perfect world, I'd like Tomcat to behave like an enterprise server, eg if it accepts a connection, it will process the request and submit the response before shutting down. A timeout should be provided (IMO unloadDelay is sufficient), for in-flight requests (including the connection stage) to complete. If this is not possible, then I would prefer the socket NOT to accept the connection, eg any connection attempt from the client (after the server shutdown has started) should result in a connection time out. This is IMO a much better approach than 503, as it is a more clear cut message to the upstream client that this server is not available, so either fail over to another server or report the error message further up stream. -- 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
