https://bz.apache.org/bugzilla/show_bug.cgi?id=64080
--- Comment #6 from carbatt...@hotmail.com --- (In reply to Christopher Schultz from comment #5) > (In reply to carbattles from comment #4) > > @Christopher Schultz In the previous bug 62515 I mentioned the first thing > > that should happen, when a shutdown is requested, is that the port should be > > closed, so no more incoming requests are accepted. > > Closing the port will terminate all the connections, including those > in-flight. > > > Then in-flight requests should be executed to completion based on timeout. > > Not possible. > > > This bug is about that this is only partially implemented, as the port is > > partially closed as the first thing, it still accepts connect requests, but > > fails when the client tries to submit the request payload (eg on a POST). > > There is no such thing as "partially closed". The port is either bound or > not. When unbinding, everything is lost. So you either wait and possibly > never close or you close and possibly drop connections in the backlog. I understand what you are saying, but this is how most enterprise servers does it. Quote from WebSphere: >WebSphere Application Server supports three shutdown modes: stop, stop >immediate and terminate (in order of immediacy). > >A normal stop begins by preventing new inbound HTTP and IIP requests and then >has a quiesce period in which in-flight requests are allowed to complete. The >maximum time allowed for these requests to complete is 180 seconds >(configurable via a JVM property). This maximum is enforced regardless of >whether or not a request is part of a global transaction. At the end of this >period the application server components (including any in-process messaging >engine) then begin to shutdown. -- 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
