Thanks to everyone for their responses.
I probably should have mentioned a little bit about our application
architecture. The client is a Java Applet and all requests to server are
made using Java HttpConnection. We have not had this problem when we ran on
JRun. At times, we had a request run for 4+ hours and still came back with
results. Only switching to Tomcat put the 5 minute restriction on us. The
application is used by scientists and depending on number of datapoints they
select, the analysis could run well over an hour at times. As you can see,
there is no web page involved to keep refreshing. True, we could redesign
our application if we have time and money.
However, I am looking for some configuration change that would help me solve
this problem quickly.
-Original Message-
From: Sexton, George [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 11, 2002 9:55 AM
To: Tomcat Users List
Subject: RE: Request/Connection Timeout
As others have said, you need to re-design your app. Personally, I would
initiate the computation in a background thread and mail the results to the
user as a PDF document. Further, I would use a queue design so that only
one computation is running at a time. What will your app do if the user hits
back, and keeps re-submitting? What will your app do if Monday morning, 40
managers come in and request a big report?
George Sexton
MH Software, Inc.
Home of Connect Daily Web Calendar Software
http://www.mhsoftware.com/connectdaily.htm
Voice: 303 438 9585
-Original Message-
From: GUNTURU, SRINIVAS [AG-Contractor/1000]
[mailto:[EMAIL PROTECTED]]
Sent: 11 December, 2002 8:28 AM
To: '[EMAIL PROTECTED]'
Subject: Request/Connection Timeout
Hi,
We are using Tomcat 4.0.4 on Apache. Right now when we have a request that
takes longer than 300 seconds(5 minutes), connections are timing out and we
are getting various errors. How do we go about increasing this timeout so
that the request does not timeout. Unfortunately, The analysis that runs on
the server is very computational intensive and we have done a lot of tuning
and most of the times it does run under 5 minutes however depending on
server load and database load we do run over 5 minutes frequently and error
out. Ideally, we would like to not have this restriction. I have searched
in the archives and Tomcat documentation and have not found anything.
Thanks for your help.
Srinivas
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
