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=10527>. 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=10527 ------- Additional Comments From [EMAIL PROTECTED] 2006-05-26 13:16 ------- Created an attachment (id=18354) --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18354&action=view) Tomcat thread hung on handshake Server.xml <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="8443" minProcessors="5" maxProcessors="75" enableLookups="true" acceptCount="100" debug="0" scheme="https" secure="true" useURIValidationHack="false" disableUploadTimeout="true"> <Factory className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory" clientAuth="false" keystoreFile="/omcsw/27.0.2.8.00/lib/3pt/bes/var/domains/base/configurations/EMF/mos/presentation/Client_iEMS/appl/iemsKeystore" keystorePass="lucent" protocol="TLS"/> </Connector> We found that this is happening in our setup here. All the connections were fine and then after some time the tomcat was slow in responding and then it stopped responding. We believe it is because our maxProcessors was set to 75 and we can see there were 74 threads on handshake running. So we understand the server slowness could be of high number of threads but what we do not understand is why the threads are performing socket read and why there is no time out. If it is not a tomcat problem any clue on what client configuration could be wrong will be helpful. -- 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]
