DO NOT REPLY [Bug 14994] - https coyote connector leaving sockets in CLOSE_WAIT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=14994.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=14994
--- Additional Comments From [EMAIL PROTECTED] 2005-07-08 14:53 ---
I am not facing this problem on tomcat 5.5.9 :) may be it is resolved now.
(In reply to comment #6)
Here's a real easy test case.
1. Configure an https service.
2.
import java.io.*;
import java.text.*;
import java.util.*;
import javax.servlet.http.*;
public class test extends HttpServlet
{
public void doGet(HttpServletRequest request, HttpServletResponse
response)
throws IOException
{
PrintWriter out = null;
try
{
response.setContentType(text/plain);
response.setDateHeader(Expires, 0);
response.setHeader(Pragma, no-cache);
out = response.getWriter();
out.println(Hello There);
for (int i = 0 ; i 2000 ; i ++)
out.println(Math.random());
}
catch (Exception e)
{
e.printStackTrace();
}
}
}
Fire it up.
3. Start IE or Mozilla and aim it at page.
4. Hold F5 button down for 10 seconds.
5. netstat -anp
tcp1 0 63.127.110.16:443 63.127.110.14:4499
CLOSE_WAIT
10860/java
tcp1 0 63.127.110.16:443 63.127.110.14:4498
CLOSE_WAIT
10860/java
tcp1 0 63.127.110.16:443 63.127.110.14:4497
CLOSE_WAIT
etc. etc.
Dead and stays that way for at least three hours (as long as I could leave
it).
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14994] - https coyote connector leaving sockets in CLOSE_WAIT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994 https coyote connector leaving sockets in CLOSE_WAIT [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-28 02:17 --- Appears to be fixed as of 4.1.24. There is a note on the main webpage about a fix for SSL users regarding a denial of service bug. I guess this is it as it no longer hangs. No more information anywhere except in the changelog which is also pretty vague. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14994] - https coyote connector leaving sockets in CLOSE_WAIT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994
https coyote connector leaving sockets in CLOSE_WAIT
--- Additional Comments From [EMAIL PROTECTED] 2003-02-24 17:19 ---
Here's a real easy test case.
1. Configure an https service.
2.
import java.io.*;
import java.text.*;
import java.util.*;
import javax.servlet.http.*;
public class test extends HttpServlet
{
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws IOException
{
PrintWriter out = null;
try
{
response.setContentType(text/plain);
response.setDateHeader(Expires, 0);
response.setHeader(Pragma, no-cache);
out = response.getWriter();
out.println(Hello There);
for (int i = 0 ; i 2000 ; i ++)
out.println(Math.random());
}
catch (Exception e)
{
e.printStackTrace();
}
}
}
Fire it up.
3. Start IE or Mozilla and aim it at page.
4. Hold F5 button down for 10 seconds.
5. netstat -anp
tcp1 0 63.127.110.16:443 63.127.110.14:4499 CLOSE_WAIT
10860/java
tcp1 0 63.127.110.16:443 63.127.110.14:4498 CLOSE_WAIT
10860/java
tcp1 0 63.127.110.16:443 63.127.110.14:4497 CLOSE_WAIT
etc. etc.
Dead and stays that way for at least three hours (as long as I could leave it).
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14994] - https coyote connector leaving sockets in CLOSE_WAIT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994 https coyote connector leaving sockets in CLOSE_WAIT [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2003-02-12 14:12 --- The possibility to set the socket linger? Is this a setting somwhere? Regarding it not being a problem, I've let it go as long as 3 days and the sockets are not recycled. Seems like a definite DoS problem when all I have to do is hammer the Refresh button on my browser for 30 seconds and I'll reach the acceptCount number of connections with CLOSE_WAIT's, thereby refusing connection for all other users for at least 3 days (and probably forever). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14994] - https coyote connector leaving sockets in CLOSE_WAIT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994 https coyote connector leaving sockets in CLOSE_WAIT --- Additional Comments From [EMAIL PROTECTED] 2003-02-12 15:16 --- We have recently experimented with Coyote and HTTPS. The symptoms we encountered are very similar to those described by Mike. After a very limited time HTTPS is blocked completely and never serves any further requests. (In our case, due to lack of time at the moment, we have simply reverted to the old deprecated https connector. I can thus unfortunately not supply any further information. This comment should be considered merely a FYI.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14994] - https coyote connector leaving sockets in CLOSE_WAIT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994 https coyote connector leaving sockets in CLOSE_WAIT [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED OS/Version|HP-UX |Linux Resolution|INVALID | Version|4.1.12 |4.1.18 --- Additional Comments From [EMAIL PROTECTED] 2003-02-11 21:58 --- This is actually Redhat Linux 6.2, not HP_UX. I upgraded to Tomcat 4.1.18 and it's still occurring. Andi Kleen (a developer for SuSE) says at http://www.uwsg.iu.edu/hypermail/linux/kernel/0204.0/0053.html that it's not a OS problem if the CLOSE_WAIT's go away when I kill the process, which they do. 'netstat -apo' shows that the CLOSE_WAIT connections have no timer on them. I can reproduce the problem by: - go to any https url a browser - repeatedly click refresh very quickly in a browser Additional Log Info - Broken pipe message no longer appear with 4.1.18 - catalina message: [INFO] ThreadPool - -All threads are busy, waiting. Please increase maxThreads or check the servlet status75 75 My system: - Tomcat 4.1.18 (and 4.1.12) - Redhat Linux 6.2, kernel 2.2.19 - IBM JVM, 1.3.1 r1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14994] - https coyote connector leaving sockets in CLOSE_WAIT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994 https coyote connector leaving sockets in CLOSE_WAIT [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-02-12 07:52 --- I added the possibility to set the socket linger recently. Well, the thing is that either it fixes the problem (which wasn't one, you're just not giving enough time to the server to close the socket; everything gets recycled eventually), or it cannot be fixed (other than closing the socket, I don't see what Tomcat can do). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14994] - https coyote connector leaving sockets in CLOSE_WAIT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994 https coyote connector leaving sockets in CLOSE_WAIT [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-12-02 19:42 --- CLOSE_WAIT means that it's waiting for an ACK of the close. In most systems, you can configure the maximum amount of time that a socket remains in CLOSE_WAIT before it's forced close. However, I don't use HP-UX, so I don't know the command it uses. In any case, it's not something that Tomcat has any control over. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
