tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadole, Nishant IN BOM SISL" <Nishant.Had...@siemens.com>
Subject RE: Tomcat Crashes out of continuous servicing of stuck request
Date Mon, 07 Dec 2009 04:19:21 GMT
Dear Chris,

Tomcat crashes means, the free memory starts declining dramatically to zero, and server stops
responding to new requests. I am sure with little modifications, this can be handled in code
itself, and this is not a concern at all.

I am more interested in knowing whether there exists any configuration for such cases, which
stops processing after some predefined time-out. I know that this can be done for KEEPALIVE
requests. What @ requests in SERVICE stage.

The screenshot for Tomcat Manager is attached for the same.

With best regards,
Nishant Hadole
 
Siemens IT Solutions and Services
SIS PRO SI-I
Tel.: +91 22 2495 7816
Fax: +91 22 6660 8521
Mailto: Nishant.Hadole@siemens.com
www.siemens.co.in
-----Original Message-----
From: Christopher Schultz [mailto:chris@christopherschultz.net] 
Sent: Saturday, 05 December, 2009 03:34 AM
To: Tomcat Users List
Cc: Hadole, Nishant IN BOM SISL
Subject: Re: Tomcat Crashes out of continuous servicing of stuck request

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nishant,

On 12/4/2009 4:29 AM, Hadole, Nishant IN BOM SISL wrote:
> Tomcat continues processing request indefinitely, causing loss of
> free heap memory and eventually crashes.

When you say "crashes", what exactly to you mean? OOME? JVM failure?

> When checked in Tomcat Monitor, under header jk-8009, the stage for
> stuck request is SERVICE and time goes on increasing.

As others have said, without attempting to send data to the client, you
can't know that they have disappeared. :(

My question is why your code causes a "crash" when the client
disappears, but works just fine when the client gets a proper response.
That suggests a mismanagement of resources by your webapp. You might
consider reviewing your code to find out why your "loss of free heap
memory" is occurring, because Tomcat surely isn't causing that to happen.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksZh0sACgkQ9CaO5/Lv0PBGfwCfVjYr8P9A0iFm6hLKkG7gxKx6
zsoAn2s5Box8os9g0dE6uFgB4TXJWPdr
=ssOC
-----END PGP SIGNATURE-----
Mime
View raw message