Hi, I am in the process of changing my JK connector from Ajp13Connector to CoyoteConnector. I have encountered some weird behaviors with the new Connector that never happens with the old one. Since I do a lot of Applet-Servlet communication via HttpURLConnection, I've getting StreamCorruptedException and EOFException randomly when the client side has slow connection with the old connector (yes, I do it with java Object IO). After I migrate to the new Connector, those symptoms are gone but I get SocketTimeoutException with read timeout instead. And when it happens, tomcat usually stops taking new incoming requests for a while. So the new connector doesn't really help to solve my problems.
My guess is that when the SocketTimeoutException happens, the ajp processor (or the underlying socket connection) doesn't release immediately somehow, and after a couple of SocketTimeoutExceptions the Tomcat uses up all its processors (or connections) so it will not take more requests till those resources are released. My temporary workaround for this is to set the Connector timeout to infinity with the mod_jk recycle timeout to 600 to avoid any hang connection. But I don't know whether there will be any ill effects about this settings. If anyone has any insight or solution for this problem please let me know. Thank you, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]