query($sql, MYSQLI_ASYNC | MYSQLI_USE_RESULT);
$links = $errors = $reject = [];
$links[] = $mysqli;
// wait up to 1.5 seconds
$seconds = 1;
$microseconds = 500000;
$timeStart = microtime(true);
if (mysqli_poll($links, $errors, $reject, $seconds, $microseconds) > 0) {
echo "query finished executing. now we start fetching the data rows over the network...\n";
$result = $mysqli->reap_async_query();
if ($result) {
while ($row = $result->fetch_row()) {
// print_r($row);
if (microtime(true) - $timeStart > 1.5) {
// we exceeded our time limit in the middle of fetching our result set.
echo "timed out while fetching results\n";
var_dump($mysqli->close());
break;
}
}
}
} else {
echo "timed out while waiting for query to execute\n";
// kill the thread to stop the query from continuing to execute on
// the server, because we are abandoning it.
var_dump($mysqli->kill($mysqli->thread_id));
var_dump($mysqli->close());
}
The flags I'm giving to
mysqli_query accomplish important things. It tells the client driver to enable asynchronous mode, while forces us to use more verbose code, but lets us use a timeout(and also issue concurrent queries if you want!). The other flag tells the client not to buffer the entire result set into memory.
By default, php configures its mysql client libraries to fetch the entire result set of your query
into memory before it lets your php code start accessing rows in the result. This can take a long time to transfer a large result. We disable it, otherwise we risk that we might time out while waiting for the buffering to complete.
Note that there's two places where we need to check for exceeding a time limit:
The actual query execution
while fetching the results(data)
You can accomplish similar in the PDO and regular mysql extension. They don't support
asynchronous queries, so you can't set a timeout on the query execution time. However, they do support unbuffered result sets, and so you can at least implement a timeout on the fetching of the data.
For many queries, mysql is able to start streaming the results to you almost immediately, and so unbuffered queries alone will allow you to somewhat effectively implement timeouts on certain queries. For example, a
select * from tbl_with_1billion_rows
can start streaming rows right away, but,
select sum(foo) from tbl_with_1billion_rows
needs to
process the entire table before it can start returning the first row to you. This latter case is where the timeout on an asynchronous query will save you. It will also save you from plain old deadlocks and other stuff.
ps - I didn't include any timeout logic on the connection itself.
Lagi enak-enak ngoding pake database Mysql tiba-tiba error gak bisa buka PhpMyadmin ?
Selow gans.. simak tutorial simple ini. 100% TESTED By Ane. heheh..
LANGKAH 1 Buka Control Panel Mysql, klik Config pada Apache, kemudian pilih
PHP.ini
LANGKAH 2 Setelah terbuka, cari teks max_execution_time = 30. Ubah angka 30 nya menjadi 0, kemudian SAVE.
SELESAI... Kalau masih muncul pesan error juga, coba bersihkan dulu cache browser kamu. Kalau ada pertanyaan, komen aja gan/sist.. ;)
(PHP 4, PHP 5, PHP 7, PHP 8)
Table of Contents
Description
Return Values
How do you fix maximum execution time of 120 seconds exceeded?
How do you fix max execution time of 30 seconds exceeded?
What is the maximum value of max_execution_time?
How can we increase maximum execution time of 60 seconds exceeded in xampp?
set_time_limit
— Limits the maximum execution time
Description
set_time_limit(int$seconds): bool
When called, set_time_limit() restarts the timeout counter from zero. In other words, if the timeout is the default 30 seconds, and 25 seconds into script execution a call such as set_time_limit(20) is made, the script will run for a total of 45 seconds before timing out.
Parameters
seconds
The maximum execution time, in seconds. If set to zero, no time limit is imposed.
Return Values
Returns true on success, or false on failure.
Notes
Note:
The set_time_limit() function and the configuration directive max_execution_time only affect the execution time of the script itself. Any time spent on
activity that happens outside the execution of the script such as system calls using system(), stream operations, database queries, etc. is not included when determining the maximum time that the script has been running. This is not true on Windows where the measured time is real.
mba_aslam at yahoo dot com ¶
15 years ago
while setting the set_time_limit(), the duration of sleep() will be ignored in the execution time. The following illustrates:
Both set_time_limit(...) and ini_set('max_execution_time',...); won't count the time cost of sleep,file_get_contents,shell_exec,mysql_query etc, so i build this function my_background_exec(), to run static method/function in background/detached process and time is out kill it:
my_exec.php: function my_background_exec($function_name, $params, $str_requires, $timeout=600) {$map=array('"'=>'\"', '$'=>'\$', '`'=>'\`', '\\'=>'\\\\', '!'=>'\!'); $str_requires=strtr($str_requires, $map); $path_run=dirname($_SERVER['SCRIPT_FILENAME']); $my_target_exec="/usr/bin/php -r \"chdir('{$path_run}');{$str_requires} \\\$params=json_decode(file_get_contents('php://stdin'),true);call_user_func_array('{$function_name}', \\\$params);\""; $my_target_exec=strtr(strtr($my_target_exec, $map), $map); $my_background_exec="(/usr/bin/php -r \"chdir('{$path_run}');{$str_requires} my_timeout_exec(\\\"{$my_target_exec}\\\", file_get_contents('php://stdin'), {$timeout});\" <&3 &) 3<&0";//php by default use "sh", and "sh" don't support "<&0" my_timeout_exec($my_background_exec, json_encode($params), 2); }
You can do set_time_limit(0); so that the script will run forever - however this is not recommended and your web server might catch you out with an imposed HTTP timeout (usually around 5 minutes).
You should check your web server's guides for more information about HTTP timeouts.
Jonathon
eric pecoraro at shepard com ¶
17 years ago
I was having trouble with script timeouts in applications where the user prompted long running background actions. I wrote this cURL/CLI background script that solved the problem when making requests from HTTP.
/* BACKGROUND CLI 1.0
eric pecoraro _at_ shepard dot com - 2005-06-02 Use at your own risk. No warranties expressed or implied.
Include this file at the top of any script to run it in the background with no time limitations ... e.g., include('background_cli.php');
The script that calls this file should not return output to the browser. */ # REQUIREMENTS - cURL and CLI
if ( !function_exists('curl_setopt') OR !function_exists('curl_setopt') ) { echo 'Requires cURL and CLI installations.' ; exit ; }# BUILD PATHS $script = array_pop(explode('/',$SCRIPT_NAME)) ; $script_dir = substr($SCRIPT_NAME,0,strlen($SCRIPT_NAME)-strlen($script)) ; $scriptURL = 'http://'. $HTTP_HOST . $script_dir . "$script" ; $curlURL = 'http://'. $HTTP_HOST . $script_dir . "$script?runscript=curl" ;# Indicate that script is being called by CLI if ( php_sapi_name() == 'cli' ) { $CLI = true ; }# Action if script is being called by cURL_prompt() if ( $runscript == 'curl' ) { $cmd = "/usr/local/bin/php ".$PATH_TRANSLATED ; // server location of script to run exec($cmd) ; exit; }# USER INTERFACE // User answer after submission. if ( $post ) { cURL_prompt($curlURL) ; echo '
Background CLI'; echo 'O.K. If all goes well, '.$script.' is working hard in the background with no ' ; echo 'timeout limitations.
; echo '
' ; exit ; } // Start screen. if ( !$CLI AND !$runscript ) { echo 'Background CLI
' ; echo '; echo 'Click to run '.$script.' from the PHP CLI command line, in the background.
' ; echo '' ; echo '
' ; exit ; }# cURL URL PROMPT FUNCTION function cURL_prompt($url_path) { ob_start(); // start output buffer $c=curl_init($url_path); curl_setopt($c, CURLOPT_TIMEOUT, 2); // drop connection after 2 seconds curl_exec($c); curl_close($c); ob_end_clean(); // discard output buffer } ?>
Anonymous ¶
2 years ago
if you want to check how much time remains, this should work (at least on Windows, on non-Windows platforms, i'm not sure)
gives you number of seconds until the script will be terminated due to the time limit. (tested on Windows 7 X64 SP1 with PHP 7.3.7) - or gives you null if there is no time limit.
robertbrogers at gmail dot com ¶
8 years ago
Documentation states: When called, set_time_limit() restarts the timeout counter from zero. In other words, if the timeout is the default 30 seconds, and 25 seconds into script execution a call such as set_time_limit(20) is made, the script will run for a total of 45 seconds before timing out.
If I have a long running script and i want a exact time limit, I set this as near as possible to the first line.
php at mightycpa.com ¶
19 years ago
You may also need to look at Apache's timeout setting (Win32 version for me), I changed max execution time value in php.ini, and still got stopped by Apache's timeout value in the httpd.conf file.
If you would like to calculatue the wall time of your script (includes all external DB/HTTP calls etc.) in Unix (in Windows this is already default behavior), you could use the following function:
$timeoutInSeconds
= 3;// This will make sure this is always called async pcntl_async_signals(1); // Second parameter is any callable (https://www.php.net/manual/en/language.types.callable.php) pcntl_signal(SIGALRM, function() { exit('Stop it!'); }); pcntl_alarm($timeoutInSeconds); ?>
rycardo74 at gmail dot com ¶
16 years ago
this work to fine html streaming AND time pass limit
One thing that I wish I had found sooner is, if you're using php-cli and really need to limit the executation time, and if you're in *nix, you can use "timeout" which is part of coreutils. For example:
timeout 5 /usr/bin/php -q /path/to/script
and it will kill it if it takes longer than 5 seconds. I had a few quick php scripts I wrote for use with cacti for example.
rsallo at gna dot NOSPAM dot es ¶
19 years ago
When you are working with IIS, PHP timeout is valid only when it's lower than script timeout defined by IIS.
IIS 5 has a default timeout of 300 seconds. If you need a higher timeout, you also have to change IIS properties. Otherwise, your server will stop your PHP script before it reaches its own timeout.
php at stock-consulting dot com ¶
15
years ago
To find out the currently set time limit, use
ini_get('max_execution_time');
?>
If set_time_limit has been previously called in the script, the result will be the value which was passed to set_time_limit (and not, as the function name "ini_get" appears to suggest, the value from the php.ini file).
alexander dot krause at ed-solutions dot de ¶
11 years ago
A nice workaround to have a real max_execution_time (needs posix and pcntl):
$pid=pcntl_fork();
if (
$pid) {
//long time process
$a=0;
while (true) {
echo "a=$a\n\n";
ob_flush();
flush();
$a++;
shell_exec('sleep 10&');
}
} else {
//time-limit checker
sleep(5);
posix_kill(posix_getppid(),SIGKILL);
}
?>
jatin at jatinchimote dot com ¶
16 years ago
If you set the number of seconds to a very large number (not many ppl do that, but just in case) then php exits with a fatal error like :
Fatal error: Maximum execution time of 1 second exceeded in /path/to/your/script/why.php
[EDIT by danbrown AT php DOT net: This is due to the limit of 32-bit signed integers.]
ravenswd at gmail dot com ¶
13 years ago
Unfortunately, a script which gets into an infinite loop can produce an alarming amount of output in only a few seconds. I was attempting to debug a script, and I added
set_time_limit(2); ?>
to the beginning of the script. Unfortunately, even two seconds of run time produced enough output to overload the memory available to my browser.
So, I wrote a short routine which would limit the execution time, and also limit the amount of output returned. I added this to the beginning of my script and it worked perfectly:
set_time_limit(2);ob_start(); // buffer outputfunction shutdown () { // print only first 2000 characters of output $out = ob_get_clean(); print substr($out, 0, 2000); }register_shutdown_function('shutdown'); ?>
agvozden at gmail dot com ¶
11 years ago
If you got something like:
msg: set_time_limit() [function.set-time-limit]: Cannot set time limit in safe mode
Timeouts after five minutes in IIS on Windows are caused by an inherited CGI Timeout value of 300 seconds. This is not a PHP problem. The fix is to add custom values for the files or directories that need longer to run.
In IIS 5.0 or 7.0 (beta as of this note), you can change this value on a fairly granular level using IIS Manager, under (roughly) YOURSITE -> Properties -> Home Directory -> Configuration (button) -> Options, but in IIS 6.0, this functionality is turned off (!), so you have to get into the Metabase.
Find the site number in Metabase Explorer (e.g., 12345678), then from CMD prompt:
[get to the scripts dir] cd C:\Inetpub\AdminScripts
[this for each subdirectory from off the site root] cscript adsutil.vbs CREATE W3SVC/12345678/root/"MY SUBDIRECTORY" IIsWebDirectory
[this for the file in question] cscript adsutil.vbs CREATE W3SVC/12345678/root/"MY SUBDIRECTORY"/ILikeToTimeOut.php IIsWebFile
[this to set the timeout] cscript adsutil.vbs set W3SVC/12345678/root/"MY SUBDIRECTORY"/ILikeToTimeOut.php/CGITimeout "7200"
Note: "7200" is 2 hours in seconds, but can be whatever.
I derived the solution above from this fine article: http://www.iis-resources.com/modules/AMS/article.php? storyid=509&page=3
Silver_Knight ¶
12 years ago
if you are running a script that needs to execute for unknown time, or forever.. you may use set_time_limit(0); ..... ... .. . and at the end of the script use flush() function to tell phpto send out what it has generated.
Cleverduck ¶
16 years ago
Regarding what 'nytshadow' said, it's important to realize that max-execution-time and the set_time_limit functions measure the time that the CPU is working on the script. If the script blocks, IE: for input, select, sleep, etc., then the time between blocking and returning is NOT measured. This is the same when running scripts from the command line interface. So if you've got a log parser written in PHP that tails a file, that program WILL fail eventually. It just depends how long it takes to read in enough input to process for 30 seconds.
If you're writing a command line script that should run infinitely, setting max-execution-time to 0 (never stop) is HIGHLY recommended.
BW ¶
13 years ago
If you use Apache you can change maximum execution time by .htaccess with this line
php_value max_execution_time 200
mingalevme at gmail dot com ¶
10 years ago
If you're using PHP_CLI SAPI and getting error "Maximum execution time of N seconds exceeded" where N is an integer value, try to call set_time_limit(0) every M seconds or every iteration. For example:
require_once('db.php');$stmt = $db->query($sql);
while (
$row = $stmt->fetchRow()) { set_time_limit(0); // your code here }?>
How do you fix maximum execution time of 120 seconds exceeded?
How to Fix the Max Execution Time WordPress Error (6 Methods).
Uninstall the Problem Software. ... .
Use the WP Maximum Execution Time Exceeded Plugin. ... .
Increase the Maximum Execution Time via wp-config. ... .
Increase the Maximum Execution Time in php. ... .
Increase the Maximum Execution Time in ..
How do you fix max execution time of 30 seconds exceeded?
The
easiest solution to this problem is increasing the time limit. Changing it to 300 seconds (5 minutes) is often more than enough. If that doesn't help, you can try setting even higher values for maximum execution time.
What is the maximum value of max_execution_time?
ini_set('max_execution_time', 108000); which equals to 30 hours.
How can we increase maximum execution time of 60 seconds exceeded in xampp?
Your answer Look for : $cfg['ExecTimeLimit'] = 600;You can change '600' to any higher value, like '6000'. Maximum execution time in seconds is (0 for no limit). This will fix your error.
