http://www.mail-archive.com/tomcat-dev%40jakarta.apache.org/msg69476.html
----- Original Message ----- From: "Mladen Turk" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Sent: Monday, March 21, 2005 6:33 PM
Subject: Re: connection timeouts mod_jk 1.2.9
sander wrote:
If have added the socketTimeout option: <Connector port="8082" minProcessors="150" maxProcessors="255" enableLookups="false" acceptCount="10" debug="0" connectionTimeout="30000" disableUploadTimeout="true" socketTimeout="30000" protocol="AJP/1.3" />
It make not sense.
So, you still have 'connection timeout reached'?
Can this solve the problem: http://www.mail-archive.com/tomcat-dev%40jakarta.apache.org/msg69563.html
No, you said that the <1.2.9 behaved like that as well. So I suppose 1.2.8 and 1.2.6 do that as well?
Also inside your workers.properties you have:
# Specifies the load balance factor when used with # a load balancing worker. # Note: # ----> lbfactor must be > 0 # ----> Low lbfactor means less work done by the worker. worker.mmbase02.lbfactor=0
So why did you put lbfactor=0 if it has to be > 0? Anyhow (it will default to 1) the other worker has lbfactor=100, meaning that he will receive 100 times more requests then the other. Is it intentionally?
Regards, Mladen.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]