You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by nuka <nu...@gmail.com> on 2007/02/20 22:50:37 UTC
Re: [OT] mod_jk configuration for production
This configuration was done some time ago by someone else. I don't believe
there is a specific reason for this parameter configuration.
I believe that this should be a default dev configuration.
Rainer Jung-3 wrote:
>
> 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 weeks ago when the clients
>> received
>> http 404 errors.
>>
>> mod_jk logs have shown errors such as:
>>
>> [Tue Feb 13 08:36:03 2007][info] ajp_send_request::jk_ajp_common.c
>> (1178):
>> Socket 14 is not connected any more (errno=-1)
>> [Tue Feb 13 08:36:03 2007][info] ajp_send_request::jk_ajp_common.c
>> (1202):
>> Error sending request. Will try another pooled connection
>> [Tue Feb 13 08:36:03 2007][info] ajp_send_request::jk_ajp_common.c
>> (1225):
>> All endpoints are disconnected or dead
>> [Tue Feb 13 08:36:03 2007][info] ajp_service::jk_ajp_common.c (1749):
>> Sending request to tomcat failed, recoverable operation attempt=1
>>
>> After that, we changed the timeout for tomcat ajp connector (initially =
>> 10000) to 60000ms.
>>
>> Now we get other errors:
>>
>> - a lot of "Error decoding request" in the JBoss logs at the same times
>> where mod_jk is showing
>>
>> [Mon Feb 19 13:25:50 2007][info]
>> ajp_connection_tcp_get_message::jk_ajp_common.c (955): Tomcat has forced
>> a
>> connection close for socket 14
>> [Mon Feb 19 13:25:50 2007][error] ajp_get_reply::jk_ajp_common.c (1503):
>> Tomcat is down or refused connection. No response has been sent to the
>> client (yet)
>> [Mon Feb 19 13:25:50 2007][info] ajp_service::jk_ajp_common.c (1721):
>> Receiving from tomcat failed, recoverable operation attempt=0
>>
>> Bellow is our configuration:
>>
>> <!-- A AJP 1.3 Connector on port 8009 -->
>> <Connector port="8009" address="${jboss.bind.address}"
>> enableLookups="false" redirectPort="8443" debug="0"
>> protocol="AJP/1.3" connectionTimeout="60000"/>
>>
>> workers.properties:
>>
>> # Define list of workers that will be used
>> # for mapping requests
>> worker.list=loadbalancer, loadbalancer2, status
>>
>>
>> worker.xxxNode1.port=8109
>> worker.xxxNode1.host=xxxx
>> worker.xxxNode1.type=ajp13
>> worker.xxxNode1.socket_keepalive=True
>> worker.xxxNode1.socket_timeout=2
>> worker.xxxNode1.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.socket_keepalive=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
>>
>> Nuka
>>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/mod_jk-configuration-for-production-tf3260752.html#a9071060
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [OT] mod_jk configuration for production
Posted by nuka <nu...@gmail.com>.
I've read the documentation and my question is :
- socket_timeout = 2s but reply_timeout is 0 meaning that the webserver is
waiting forever. Which of them is used for timeout ajp connection?
Rainer Jung-3 wrote:
>
> 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 else. I don't
>> believe
>> there is a specific reason for this parameter configuration.
>> I believe that this should be a default dev configuration.
>>
>>
>>
>> Rainer Jung-3 wrote:
>>> 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 weeks ago when the clients
>>>> received
>>>> http 404 errors.
>>>>
>>>> mod_jk logs have shown errors such as:
>>>>
>>>> [Tue Feb 13 08:36:03 2007][info] ajp_send_request::jk_ajp_common.c
>>>> (1178):
>>>> Socket 14 is not connected any more (errno=-1)
>>>> [Tue Feb 13 08:36:03 2007][info] ajp_send_request::jk_ajp_common.c
>>>> (1202):
>>>> Error sending request. Will try another pooled connection
>>>> [Tue Feb 13 08:36:03 2007][info] ajp_send_request::jk_ajp_common.c
>>>> (1225):
>>>> All endpoints are disconnected or dead
>>>> [Tue Feb 13 08:36:03 2007][info] ajp_service::jk_ajp_common.c (1749):
>>>> Sending request to tomcat failed, recoverable operation attempt=1
>>>>
>>>> After that, we changed the timeout for tomcat ajp connector (initially
>>>> =
>>>> 10000) to 60000ms.
>>>>
>>>> Now we get other errors:
>>>>
>>>> - a lot of "Error decoding request" in the JBoss logs at the same times
>>>> where mod_jk is showing
>>>>
>>>> [Mon Feb 19 13:25:50 2007][info]
>>>> ajp_connection_tcp_get_message::jk_ajp_common.c (955): Tomcat has
>>>> forced
>>>> a
>>>> connection close for socket 14
>>>> [Mon Feb 19 13:25:50 2007][error] ajp_get_reply::jk_ajp_common.c
>>>> (1503):
>>>> Tomcat is down or refused connection. No response has been sent to the
>>>> client (yet)
>>>> [Mon Feb 19 13:25:50 2007][info] ajp_service::jk_ajp_common.c (1721):
>>>> Receiving from tomcat failed, recoverable operation attempt=0
>>>>
>>>> Bellow is our configuration:
>>>>
>>>> <!-- A AJP 1.3 Connector on port 8009 -->
>>>> <Connector port="8009" address="${jboss.bind.address}"
>>>> enableLookups="false" redirectPort="8443" debug="0"
>>>> protocol="AJP/1.3" connectionTimeout="60000"/>
>>>>
>>>> workers.properties:
>>>>
>>>> # Define list of workers that will be used
>>>> # for mapping requests
>>>> worker.list=loadbalancer, loadbalancer2, status
>>>>
>>>>
>>>> worker.xxxNode1.port=8109
>>>> worker.xxxNode1.host=xxxx
>>>> worker.xxxNode1.type=ajp13
>>>> worker.xxxNode1.socket_keepalive=True
>>>> worker.xxxNode1.socket_timeout=2
>>>> worker.xxxNode1.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.socket_keepalive=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
>>>>
>>>> Nuka
>>>>
>>> ---------------------------------------------------------------------
>>> To start a new topic, e-mail: users@tomcat.apache.org
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/mod_jk-configuration-for-production-tf3260752.html#a9080778
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [OT] mod_jk configuration for production
Posted by Rainer Jung <ra...@kippdata.de>.
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 else. I don't believe
> there is a specific reason for this parameter configuration.
> I believe that this should be a default dev configuration.
>
>
>
> Rainer Jung-3 wrote:
>> 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 weeks ago when the clients
>>> received
>>> http 404 errors.
>>>
>>> mod_jk logs have shown errors such as:
>>>
>>> [Tue Feb 13 08:36:03 2007][info] ajp_send_request::jk_ajp_common.c
>>> (1178):
>>> Socket 14 is not connected any more (errno=-1)
>>> [Tue Feb 13 08:36:03 2007][info] ajp_send_request::jk_ajp_common.c
>>> (1202):
>>> Error sending request. Will try another pooled connection
>>> [Tue Feb 13 08:36:03 2007][info] ajp_send_request::jk_ajp_common.c
>>> (1225):
>>> All endpoints are disconnected or dead
>>> [Tue Feb 13 08:36:03 2007][info] ajp_service::jk_ajp_common.c (1749):
>>> Sending request to tomcat failed, recoverable operation attempt=1
>>>
>>> After that, we changed the timeout for tomcat ajp connector (initially =
>>> 10000) to 60000ms.
>>>
>>> Now we get other errors:
>>>
>>> - a lot of "Error decoding request" in the JBoss logs at the same times
>>> where mod_jk is showing
>>>
>>> [Mon Feb 19 13:25:50 2007][info]
>>> ajp_connection_tcp_get_message::jk_ajp_common.c (955): Tomcat has forced
>>> a
>>> connection close for socket 14
>>> [Mon Feb 19 13:25:50 2007][error] ajp_get_reply::jk_ajp_common.c (1503):
>>> Tomcat is down or refused connection. No response has been sent to the
>>> client (yet)
>>> [Mon Feb 19 13:25:50 2007][info] ajp_service::jk_ajp_common.c (1721):
>>> Receiving from tomcat failed, recoverable operation attempt=0
>>>
>>> Bellow is our configuration:
>>>
>>> <!-- A AJP 1.3 Connector on port 8009 -->
>>> <Connector port="8009" address="${jboss.bind.address}"
>>> enableLookups="false" redirectPort="8443" debug="0"
>>> protocol="AJP/1.3" connectionTimeout="60000"/>
>>>
>>> workers.properties:
>>>
>>> # Define list of workers that will be used
>>> # for mapping requests
>>> worker.list=loadbalancer, loadbalancer2, status
>>>
>>>
>>> worker.xxxNode1.port=8109
>>> worker.xxxNode1.host=xxxx
>>> worker.xxxNode1.type=ajp13
>>> worker.xxxNode1.socket_keepalive=True
>>> worker.xxxNode1.socket_timeout=2
>>> worker.xxxNode1.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.socket_keepalive=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
>>>
>>> Nuka
>>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org