tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alessandro Bahgat <>
Subject Re: Tomcat 6.0.16 + mod_jk 1.2.19 - request threads hanging up
Date Mon, 14 Dec 2009 17:20:40 GMT
On Sat, Dec 12, 2009 at 4:57 PM, Rainer Jung <> wrote:
> On 12.12.2009 13:26, Alessandro Bahgat wrote:
>> 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.

Well, I saw that error on yesterday's logs about 25k times (roughly 1%
of the total requests) and the website isn't particularly slow these
days (it takes less than 1s to render entirely the homepage).
When it happens, we have some connections stuck in the ESTABLISHED
state with non-zero values in the Send-Q, and Java's CPU consumption
increases significantly.

We'll upgrade Apache and mod_jk and see if this anything changes.

Thank you for your help,

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message