I think the bigger question is why does it take that long to run? I can't think of too many people that are willing to wait that long for information. Personally I'd give you 30 seconds and then I'll never use something that slow again.
If you are accessing data, try adding indexes or a data redesign to speed things up. A simple index based on key data can speed up searches exponentially. Just a thought. Most of my problems have been my problems not something Tomcat was doing wrong. Robert S. Harper Information Access Technology, Inc. -----Original Message----- From: Richard Doust [mailto:[EMAIL PROTECTED] Sent: Friday, December 08, 2006 8:23 AM To: Tomcat Users List Subject: Client request times out I have a problem with a servlet running longer than 5 minutes. The client's browser is delivered an error response from somewhere on the server in an Apache/JBoss/Tomcat stack at the 5 minute mark. Does anyone know what properties/attributes in what configuration files might allow the servlet to run for longer than 5 minutes? I have tried: TimeOut (in apache config) disableUploadTimeout (in Connector attribute settings, server.xml for Tomcat 5.5) socket_timeout (in workers.properties) None seem to have the desired effect. Any help would be appreciated. Thanks. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
