marc 97/09/06 20:10:59 Modified: htdocs/manual/misc fin_wait_2.html Log: Update the fin_wait_2 page to reflect the current understanding of the issues; remove the suggestion that Apache is buggy, since no bugs have been found in that code. It now appears most likely that it is just the result of a bad interaction. The real solution, as always, is still a timeout for FIN_WAIT_2. Revision Changes Path 1.12 +12 -13 apachen/htdocs/manual/misc/fin_wait_2.html Index: fin_wait_2.html =================================================================== RCS file: /export/home/cvs/apachen/htdocs/manual/misc/fin_wait_2.html,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- fin_wait_2.html 1997/08/17 05:55:54 1.11 +++ fin_wait_2.html 1997/09/07 03:10:58 1.12 @@ -43,8 +43,8 @@
+There are numerous reasons for it happening, some of them may not +yet be fully clear. What is known follows.
+crash their server.
-One possible (and most likely) source for additional FIN_WAIT_2 states
+The most likely source for additional FIN_WAIT_2 states
is a function called
lingering_close() which was added
between 1.1 and 1.2. This function is necessary for the proper
handling of persistent connections and any request which includes
@@ -134,13 +133,13 @@
the connection has closed.
See the appendix for more details.
-We have not yet tracked down the exact reason why
lingering_close() causes problems. Its code has been
-thoroughly reviewed and extensively updated in 1.2b6. It is possible
-that there is some problem in the BSD TCP stack which is causing the
-observed problems. It is also possible that we fixed it in 1.2b6.
-Unfortunately, we have not been able to replicate the problem on our
+The code in
lingering_close() appears to cause problems
+for a number of factors, including the change in traffic patterns
+that it causes. The code has been thoroughly reviewed and we are
+not aware of any bugs in it. It is possible that there is some
+problem in the BSD TCP stack, aside from the lack of a timeout
+for the FIN_WAIT_2 state, exposed by the
+code that causes the observed problems.