× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Change the following directives in /www/zendsvr6/conf/fastcgi.conf file:
ConnectionTimeout="300" RequestTimeout="300"

These directives control connection and request timeouts in Zend Server
running in QHTTPSVR (Apache) subsystem

On Thu, Mar 12, 2015 at 6:49 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

Top line: I have a stored procedure that runs on average 1.7 minutes
before returning a result set. I put it on a PHP web page so my boss
can see these stats at her leisure instead of having to call me to
produce them. I'm getting a 408 timeout because the SP is running so long.

I have put set_time_limit(600); in my PHP
I have put max_execution_time = 300; in php.ini
I ended the ZENDSVR subsystem and restarted it
I ended the HTTP server instance and restarted it

I am working on making the stored procedure more sane but in the
interim, what do I do to tell the Zend PHP server to let my script run
longer? IBM i 7.2, PHP 5.3.3.

--
--buck

As usual I have slaughtered many electrons in vain.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.