The short answer is to not wait 15min to return the results. It's much better to use a page with a meta-refresh to check if it is done yet.
The long answer is that anyone on the food chain has the right to set a timeout. This includes the browser, any intervening proxy-servers, any native web-server (if you are running Tomcat behind it)..... A wait of 15min is almost certain to p*ss off at least one of these :). "GEESOFT" <[EMAIL PROTECTED]> wrote in message 00c501c29a71$de6b6f80$9600a8c0@art">news:00c501c29a71$de6b6f80$9600a8c0@art... Hi, I have an issue with my servlet timing out. I have just upgraded to Apache2 - ajp13 - Tomcat 4.1 configuration. I have a servlet that takes about 15 minutes to execute. Unfortunately it seems the servlet container or Apache is timing out after five minutes. The servlet stops processing and Apache returns the following html to me: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type></HEAD> <BODY><XMP></XMP></BODY></HTML> I have set: Apache - Timout to 20 minutes Tomcat workers.properties - ajp13.socketTimeout=2400 I am using the Ajp13Connector on port 8009. In the docs this connector does not seem to have a timeout. MY QUESTION Does anyone know what configuration parameter would be causing this apparent 5 minute processing timeout and can I fix this? I have all debug levels set to high and do not get any information on what is happening. I have poured through all the documentation but cannot find any information on this. I know, it is rare to expect a servlet thread to process for more than half a second. On the old Tomcat 3.2 - ajp12 - Apache 1.3 configuration did not have this problem. Thank you in advanced if someone could assist me. Regards, Glenn Drew ---------------------------------------------------------------------------- ------- Director GEESOFT PTY LTD -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
