- first create servlet which starts the computational work in a new thread.
- the servlet then redirects to another page which can monitor the progress of the computational work (and does a meta refresh every few seconds)
- when the computational work is done - redirect to your real results
Or you can use a multipart response .... where the first part(s) are messages saying work is being done. Get a demo of Keynote web monitoring services for a similar concept.
Good luck, tasks like this are always a pain in the rear.
-Tim
GUNTURU, SRINIVAS [AG-Contractor/1000] wrote:
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]>
