Bug #17818 Updated: Maximum Execution Time exceeded

From: Date: Tue, 18 Jun 2002 22:05:48 +0000
Subject: Bug #17818 Updated: Maximum Execution Time exceeded
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-11210@lists.php.net to get a copy of this message
ID: 17818 Updated by: sniper@php.net Reported By: clay@incogen.com -Status: Open +Status: Feedback Bug Type: PHP options/info functions Operating System: SunOS jabba 5.7 Generic_106541-1 PHP Version: 4.2.1 New Comment: So this happens ONLY with that one script? Previous Comments: ------------------------------------------------------------------------ [2002-06-18 17:44:07] clay@incogen.com Don't we all wish it were that easy. The script that is causing this problem is pulling large datasets from Oracle, calling all sorts of libraries, its an insane machine of scripts. I think this (the OCI usage)is probably were the problem originates. However, I am concerned that the error message does not reflect the time out value. Is the error message hard-coded to 30 seconds? phpInfo() knows the max execution time value that I have set, so why doesn't the error message? ------------------------------------------------------------------------ [2002-06-18 17:38:45] sniper@php.net Please add a short example script here which causes this problem. ------------------------------------------------------------------------ [2002-06-18 12:44:21] clay@incogen.com I'm using apache 1.34 ------------------------------------------------------------------------ [2002-06-18 12:38:21] clay@incogen.com The phpInfo shows the appropriate value, The script takes about a minute ( or a few minutes ) to run, then shows the error. I have restarted apache, I have stopped and started apache. ------------------------------------------------------------------------ [2002-06-18 12:35:45] sander@php.net Does phpinfo() show the appropriate values? Restart your webserver if necessary. Does it take 30 seconds to come up with that message or does it show that at once? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/17818 -- Edit this bug report at http://bugs.php.net/?id=17818&edit=1

« previous php.bugs (#11210) next »