Tomcat 4.1.24 and Coyote JK2 Connector
I've upgraded this morning to Tomcat 4.1.24 from 4.1.18. On 4.1.18, I was connecting to Apache using the following configuration in server.xml: Connector className=org.apache.ajp.tomcat4.Ajp13Connector acceptCount=10 bufferSize=2048 connectionLinger=-1 connectionTimeout=-1 debug=0 enableLookups=false maxProcessors=75 minProcessors=5 port=11009 redirectPort=-1 scheme=http secure=false tomcatAuthentication=true I tried moving to the newer connector for Tomcat 4.1.24: !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ But I get the following message in my log file. If this is not an issue (which I don't think it is b/c it's an INFO), how do I turn this log message off? Mar 24, 2003 10:42:40 AM org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached Do I just set the connectionTimeout to -1? Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.24 and Coyote JK2 Connector
Not sure about your specific problem, but I noticed you had tomcatAuthentication=true on your old AJP13Connector config. That config has been moved to the jk2.properties file for both mod_jk and jk2. Just add the following to your jk2.properties request.tomcatAuthentication=true actually, since it is currently set to true, you don't even need to specify it, but if you did want to get the remote user from the connectors rather than Tomcat, then do... request.tomcatAuthentication=false Just thought you might want to know that. Jake At 10:45 AM 3/24/2003 -0700, you wrote: I've upgraded this morning to Tomcat 4.1.24 from 4.1.18. On 4.1.18, I was connecting to Apache using the following configuration in server.xml: Connector className=org.apache.ajp.tomcat4.Ajp13Connector acceptCount=10 bufferSize=2048 connectionLinger=-1 connectionTimeout=-1 debug=0 enableLookups=false maxProcessors=75 minProcessors=5 port=11009 redirectPort=-1 scheme=http secure=false tomcatAuthentication=true I tried moving to the newer connector for Tomcat 4.1.24: !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ But I get the following message in my log file. If this is not an issue (which I don't think it is b/c it's an INFO), how do I turn this log message off? Mar 24, 2003 10:42:40 AM org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached Do I just set the connectionTimeout to -1? Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.1.24 and Coyote JK2 Connector
But I get the following message in my log file. If this is not an issue (which I don't think it is b/c it's an INFO), how do I turn this log message off? Mar 24, 2003 10:42:40 AM org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached Do I just set the connectionTimeout to -1? this is due to the stupidity of the tomcat-programmers. just ignore these messages. i'm currently writing my own connector to overcome this problem (the source of the current connector is too confusing to be improved) but i'm still missing people that can write apache-modules, so it only become yet another ajp13 implementation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
