tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Tomcat Crashes out of continuous servicing of stuck request
Date Tue, 08 Dec 2009 15:30:56 GMT
Hash: SHA1


Mailing the list is fine: there's no need to mail me separately.

On 12/6/2009 11:19 PM, Hadole, Nishant IN BOM SISL wrote:
> Tomcat crashes means, the free memory starts declining dramatically 
> to zero, and server stops responding to new requests.

Does the JVM and/or Tomcat actually crash? That's an important
difference: if Tomcat simply stops responding to requests, that's likely
to be a different problem than an actual crash.

> I am sure with little modifications, this can be handled in code
> itself, and this is not a concern at all.

Eh... okay, if you say so.

> 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.

I'm not sure what you mean, here.

> The screenshot for Tomcat Manager is attached for the same.

The screenshot indicates that you have 756MiB free of a 1016MiB heap.
That looks good to me. It also indicates that your "jvehelp" servlet
seems to be taking forever to do its work. Perhaps you should take a
thread dump and figure out what your servlet is doing when it stalls?

Only one thread is in the "keepalive wait" state, and it has been there
for 6.5 seconds. What is your keepalive timeout? Is it set to an
appropriate amount?

- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


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

View raw message