"Richard Doust" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Well, it's a complicated report used by a purchaser to generate a > purchase order based on need for a product dependent on customer demand. > It's accessing a LOT of data. That's not to say that I can't speed it up > with indexes, or break it up into a request that's passed off to a server > process that generates data that it then writes to the database for later > retrieval by the client. But it wasn't designed that way and such a > change would be substantial. It has worked for a few years, and what I'm > looking to do right now is get around the 5 min. barrier before spending > more time looking at the underlying problem and ways to solve it. > Thanks for your suggestion.
Unfortunately, you probably won't find anything that works. The reason is that it is probably the browser that is giving up and closing the connection. With the latest Tomcat/mod_jk, it might be possible if you can send a few KB of data and flush it to keep the browser from flushing it on you. But this still isn't a fix, because if the user is behind a proxy, the proxy may try and read the entire body (so the browser sees it as taking too long), or simply time out because the total request is taking too long. > > On Dec 8, 2006, at 10:42 AM, Robert Harper wrote: > >> 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] >> > > > --------------------------------------------------------------------- > 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]
