tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <rainer.j...@kippdata.de>
Subject Re: Tomcat 6.0.16 + mod_jk 1.2.19 - request threads hanging up
Date Sat, 12 Dec 2009 15:57:14 GMT
On 12.12.2009 13:26, Alessandro Bahgat wrote:
> On Fri, Dec 11, 2009 at 4:27 PM, Rainer Jung<rainer.jung@kippdata.de>  wrote:
>> On 09.12.2009 12:18, Pid wrote:
>>>
>>> It could be, but while you're upgrading you might consider upgrading
>>> HTTPD to the best available version too, 2.0.52 release date: 1 Oct
>>> 2004. (That's 35 internet years ago.)
>>
>> ... and mod_jk 1.2.19 dates back to September 2006, so according to your
>> math 21 internet years ago. There were so many bugs fixed since then, that
>> you'll hardly find anyone that really tries to help debugging those old
>> versions. At least use a recent mod_jk and look at
>>
>> http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html
>>
>> for some important hints about configuration.
>
> Thank you both for your advice. I'm pushing towards upgrading the
> Apache+mod_jk stack as well.
> Our last tests with the latest Tomcat and mod_jk still showed a lot of
> CPU time being spent in sendbb methods, with some threads being stuck
> in that method for long time.
>
> We actually found out a lot of "unrecoverable error 200, request
> failed" error messages in the mod_jk log (roughly around 1k per hour),
> so I'm starting to wonder if there's any issue with the firewalls and
> the network infrastructure. What would you think about that?
>
> [Thu Dec 03 16:58:52 2009][31539:42688] [info]
> service::jk_lb_worker.c (873): unrecoverable error 200, request
> failed. Client failed in the middle of request, we can't recover to
> another instance.
> [Thu Dec 03 16:58:52 2009][31539:42688] [info]  jk_handler::mod_jk.c
> (2056): Aborting connection for worker=applprod

The above two lines belong together, the next lines are something 
different. The pait [pid:tid} changed.

The above lines are logged, whenever there was a problem sending back 
gthe response from Apache to the client/browser. It may happen, if a 
user in the meatime clicked on something else or pressed the reload 
button. If you get it a lot, maybe your app is to slow, your users are 
to nervous, or indeed there might be a network problem. Occasional 
occurrences are normal.

> [Thu Dec 03 16:58:53 2009][31612:42688] [info]
> jk_open_socket::jk_connect.c (450): connect to XXX.XXX.XXX.XXX:8009
> failed with errno=111
> [Thu Dec 03 16:58:53 2009][31612:42688] [info]
> ajp_connect_to_endpoint::jk_ajp_common.c (872): Failed opening socket
> to (XXX.XXX.XXX.XXX:8009) with (errno=111)
> [Thu Dec 03 16:58:53 2009][31612:42688] [info]
> ajp_send_request::jk_ajp_common.c (1247): (applprod05) error
> connecting to the backend server (errno=111)
> [Thu Dec 03 16:58:53 2009][31612:42688] [info]
> ajp_service::jk_ajp_common.c (1867): (applprod05) sending request to
> tomcat failed,  recoverable operation attempt=1

errno 111 is "Connection refused", so either your Tomcat was down or 
something else blocked the connection.

Regards,

Rainer


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message