xxNode1.recycle_timeout=300
>>>> worker.xxxNode1.recovery_options=0
>>>>
>>>> worker.xxxNode2.port=8209
>>>> worker.xxxNode2.host=xxx.xx.xx.xx
>>>> worker.xxxNode2.type=ajp13
>>>> worker.xxxNode2
>
> worker.xxxNode2.port=8209
> worker.xxxNode2.host=xxx.xx.xx.xx
> worker.xxxNode2.type=ajp13
> worker.xxxNode2.socket_keepalive=True
> worker.xxxNode2.socket_timeout=2
> worker.xxxNode2.recycle_timeout=300
> worker.xxx2.recovery_options=0
>
&g
Then start reading on
http://tomcat.apache.org/connectors-doc/reference/workers.html
what your configuration means. You will notice, that a value of 2 for
the socket_timeout does not really make any sense.
Regards,
Rainer
nuka schrieb:
> This configuration was done some time ago by someone els
=True
>> worker.xxxNode2.socket_timeout=2
>> worker.xxxNode2.recycle_timeout=300
>> worker.xxx2.recovery_options=0
>>
>> Do you have any idea which parameters do we need to change in this
>> configuration?
>>
>> thanks
>>
>> rgds
>
What's your idea why you configured a socket timeout of 2?
nuka schrieb:
> Hello,
>
> I am facing to a problem concerning apache-tomcat configuration via mod_jk
> for our production environment. We are using Apache: 2.0.55, Tomcat 5.0,
> mod_jk 1.2.15.
>
> Our first problem has been raised some
message in context:
http://www.nabble.com/mod_jk-configuration-for-production-tf3260752.html#a9062426
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsu
