Hi, thanks for your reply. However I don't think its the browser timing out.
We get the "Internal Servlet Error - read timeout" thrown from Tomcat which
is the response displayed in the browser. This problem is shown when Tomcat is
under load, i.e. 30+ concurrent users, all doing the same thing.
We dont really know if its the request/response timing out or the JVM or what.
(We do know its not the session timing out :)
We've read that in JServ there was a VM Timeout which could be set and were
wondering if there was something similar in Tomcat which could be set which
would help us.
Thanks
Andy B
-----Original Message-----
From: William Kaufman [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 18, 2001 3:17 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Setting Tomcat HTTP Request Timeout
Tomcat isn't timing out--your browser is. It gives up if it doesn't get a
response from the server in a certain amount of time. And I don't think you
can change that setting on any browser I've seen.
You could try calling ServletOutputStream.flush() each time you write data:
hopefully, that will tell the browser that you're working on it. But,
depending on your server configuration, the data might still get bufferred,
and flush() might not actually flush any data.
The only useful answer is, Don't make a servlet that takes that long.
Profile your code, calculate things ahead of time, cache results, split up
the page, do work in multiple threads, all the standard speed-up things.
-- Bill K.
> -----Original Message-----
> From: Andrew Birchall [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 18, 2001 5:25 AM
> To: [EMAIL PROTECTED]
> Subject: Setting Tomcat HTTP Request Timeout
>
>
> Hi,
> We are using a standalone Tomcat 3.2.1 for our servlet app.
> and we keep
> getting
> Error 500 read timeout errors from Tomcat on requests which
> take a long
> time.
>
> Is there any way of setting the Request timeout in Tomcat so
> we can set it
> to a
> larger value?
>
> Thanks
> Andy Birchall
> Software Developer
> Rchive-it.com
>
