Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of mike.looijmans@oce.com
 designates 65.55.88.13 as permitted sender)
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Tomcat Crashes out of continuous servicing of stuck request
Date: Fri, 4 Dec 2009 11:44:22 +0100
Message-ID: <948126CDFED9634D8B12AF27F009EDC501C87EE7@oce-exbe03-v.oce.net>
In-Reply-To: 
 <4D8250A64CBB31419B00B80AE5B319A715EF7EEF9E@INBOMW77M1MSX.in002.siemens.net>
Thread-Topic: Tomcat Crashes out of continuous servicing of stuck request
thread-index: Acp0xlLTQMXf8GmoTjKd/kn4vk/TXQAAb82AAAGcXeA=
References: 
 <4D8250A64CBB31419B00B80AE5B319A715EF7EEF9D@INBOMW77M1MSX.in002.siemens.net>
 <4B18D9DB.4050201@kippdata.de>
 <4D8250A64CBB31419B00B80AE5B319A715EF7EEF9E@INBOMW77M1MSX.in002.siemens.net>
From: "Looijmans, Mike" <mike.looijmans@oce.com>
To: "Tomcat Users List" <users@tomcat.apache.org>

Just an idea: What happens if you change your DB call into a "Sleep(30)"
or something similar? Does tomcat still misbehave then? (the 'retry'
could be related to something else than tomcat).


M

> -----Original Message-----
> From: Hadole, Nishant IN BOM SISL [mailto:Nishant.Hadole@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 client =

> press a button on JSP, it initiates a Database search =

> operation, which may take time up to 30-45 seconds. =

> Meanwhile, we are showing a screen which tell user that his / =

> her request is being processed and no to close the window. =

> =

> But, sometimes users are impatient and still close the =

> window. Yes, as you suggested, it is possible to handle close =

> event / stop processing by some notification, but application =

> is full of such utilities, and it is too much of efforts.
> =

> I am interested in some parameterization, which detects =

> broken connection and automatically drops stuck request. I =

> have even checked this with requests with STAGE as KEEPALIVE, =

> but not working with STAGE as SERVICE. Also, I am not able to =

> figure out, why the processing is repeated.
> =

> With best regards,
> Nishant Hadole
> Mailto: Nishant.Hadole@siemens.com

This message and attachment(s) are intended solely for use by the addressee=
 and may contain information that is privileged, confidential or otherwise =
exempt from disclosure under applicable law.

If you are not the intended recipient or agent thereof responsible for deli=
vering this message to the intended recipient, you are hereby notified that=
 any dissemination, distribution or copying of this communication is strict=
ly prohibited.

If you have received this communication in error, please notify the sender =
immediately by telephone and with a 'reply' message.

Thank you for your co-operation.


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