Received: from ford.rutgersinsurance.com ([38.138.71.203]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f95FxHn47644 for ; Fri, 5 Oct 2001 11:59:17 -0400 (EDT) (envelope-from aalang@rutgersinsurance.com) Received: (from root@localhost) by ford.rutgersinsurance.com (8.11.2/8.11.2) id f95Fq9i10177 for pgsql-php@postgresql.org.KAV; Fri, 5 Oct 2001 11:52:09 -0400 Received: from nj012 ([10.10.10.51]) by ford.rutgersinsurance.com (8.11.2/8.11.2) with SMTP id f95Fq9q10169 for ; Fri, 5 Oct 2001 11:52:09 -0400 Message-ID: <010a01c14db6$f57a3ca0$330a0a0a@rutgersinsurance.com> From: "Adam Lang" To: References: Subject: Re: Help with timeouts Date: Fri, 5 Oct 2001 12:01:13 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200110/28 X-Sequence-Number: 581 Ooops! I realise I sent my original answer to a wrong list. Sorry. ---------------------------------------------------------------------------- - Look at the script timeout settings in php.ini... not the httpd.conf. Send the $50 a breast cancer charity... or me. Adam Lang Systems Engineer Rutgers Casualty Insurance Company http://www.rutgersinsurance.com ----- Original Message ----- From: "Josh Berkus" To: Sent: Friday, October 05, 2001 11:26 AM Subject: Re: [PHP] Help with timeouts > Folks, > > Some answers: > > > I have a very complex database operation that can sometimes take > > 70-90 > > seconds to return results. The web page which displays the results, > > however, seems to always timeout at 60seconds despite setting the > > Apache > > timeout to 300 seconds and set_time_limit to 240. > > After a helpful web guru called us up from our post, we were able to > diagnose what's happening here (donation to be announced later): > > Regardless of the Timeout and set_time_limit() settings, most browsers > will time out at 60 seconds. > > This is obviously a huge annoyance. Therefore I am offering a *second* > charity prize to any person who can give me code (PHP or Perl) which > will display a "Processing" screen with an auto-reload to keep the > browser interested while waiting 60 to 120 seconds for a database > response in the background. *Someone* must have done this already, even > though multi-threading in PHP & Perl is nigh impossible. > > -Josh Berkus > ---------------------------------------------------------------------------- ---- > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster >