-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nishant,
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 r
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 even
-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?
> W
On 04.12.2009 11:41, Looijmans, Mike wrote:
...
Without trying to send something back to the client, there is
no way telling the client closed the window (or pressed
reload or switched to another URL).
I would expect the socket to be closed, which can be detected at the
server side. The excep
nishant.had...@siemens.com]
> Sent: vrijdag 04 december 2009 11:06
> To: 'Rainer Jung'; Tomcat Users List
> Subject: RE: Tomcat Crashes out of continuous servicing of
> stuck request
>
> Dear Rainer,
>
> Thanks for explanation. In this particular case, when cli
...
> Without trying to send something back to the client, there is
> no way telling the client closed the window (or pressed
> reload or switched to another URL).
I would expect the socket to be closed, which can be detected at the
server side. The exceptions I can think of are the client cra
...@siemens.com
-Original Message-
From: Rainer Jung [mailto:rainer.j...@kippdata.de]
Sent: Friday, 04 December, 2009 03:14 PM
To: Tomcat Users List
Cc: Hadole, Nishant IN BOM SISL
Subject: Re: Tomcat Crashes out of continuous servicing of stuck request
On 04.12.2009 10:29, Hadole, Nishant IN BOM
On 04.12.2009 10:29, Hadole, Nishant IN BOM SISL wrote:
I am using Apache HTTP Server 2.0.61, Apache Tomcat Server 6.0.14.0 and mod_jk
2.0.46 (AJP V 1.3).
mod_jk 2.0.46 does not exist.
Scenario - Client call for heavy Post request from JSP. Tomcat receives the
request and starts processing.
I am using Apache HTTP Server 2.0.61, Apache Tomcat Server 6.0.14.0 and mod_jk
2.0.46 (AJP V 1.3).
Scenario - Client call for heavy Post request from JSP. Tomcat receives the
request and starts processing. Before receiving the response, client closes JSP
window. Thus there is no one to receive
