Problem with Tomcat SSL Port 2003-10-14 - By Manty, George
Back
I am having a problem with embedded Tomcat 4.1.18. The problem is that
after some unspecified period of time Tomcat is continually opening http
processor threads that are then stuck in the CLOSE_WAIT state. I am
seeing this intermittently in Windows, HP-UX and Linux. I am using the
coyoteconnector to create both an http connector and ssl connector. The
http connector continues to work, but the SSL connector stops working.
This bug is supposed to be fixed in 4.1.24, but I question that based on
the following bugs described in these links:
http://www.mail-archive.com/tomcat-user@(protected)/msg103402.htm
l
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23311
Here are links to the related bug that was fixed:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994
>From looking at the stack trace it appears that the problem may be in
the code "org.apache.tomcat.util.threads.threadpool". When I looked at
the source for that code, there are two methods that use notify instead
of notifyall(), which is a very dangerous practice and can easily cause
the behavior I am seeing. It appears as though changing these two lines
to use notifyall() instead of notify() could fix the problem, however I
have not tested this out.
I wanted to verify that this code was changed in the latest version of
threadpool in the tomcat-util.jar file, but in the latest releases of
Tomcat I can't find the tomcat-util.jar file or the source for
ThreadPool. However, you need that file to build http11processor.java,
so it must be somewhere. Does anyone know where to find the latest
versions of tomcat-util.jar for tomcat 4.1.27? Also if anyone knows if
this code has definitely been fixed that would be helpful as well.
Thank you,
George
|
|
