#22747 [Bgs->Opn]: Getting maximum execution timeout errors on lines which shouldnt be doing so

ID: 22747 User updated by: carl at voodoomedia dot co dot uk Reported By: carl at voodoomedia dot co dot uk -Status: Bogus +Status: Open Bug Type: Scripting Engine problem Operating System: Windows 2000 SP3 PHP Version: 4.3.2-RC New Comment: But that's just a "frig", why would it be taking so long to do a session_start()? upping max execution time will just keep my users hanging there waiting for session_start to work. this is no fix to the problem at all. Previous Comments: ------------------------------------------------------------------------ [2003-04-09 05:58:35] sniper@php.net You just need to increase the max_execution_time. ------------------------------------------------------------------------ [2003-03-25 07:07:25] carl at voodoomedia dot co dot uk Hi there, I'm using Apache 1.3.27 on a windows 2000 SP3 machine, dual P3 1.6ghz processors and 1.5GB RAM PHP is loading as an apache module and i've tried 4.3.1 and 4.3.2 latest cvs binaries. the differences in my ini from php-dist are short_open_tags = Off precision = 14 zlib_output_compression = on (but only did this last night wsa off until then) allow_call_time_pass_reference = off max_execution_time = 40 error_reporting = E_ALL display_errors = Off log_errors = On ignore_repeated_errors = on error_log = e:\php.log register_argc_argv = off magic_quotes_runtime = on include_path = e:\www\ doc_root = e:\www\ extensions_dir = c:\php\extensions upload_max_file_size=4M default_socket_timeout=30 SMTP=[ip to local smtp server] session_save_path = c:\php\sessions session.gc_dividend = 1000 session.bug_compat_warn = 0 (makes no difference, still see em) Thanks ------------------------------------------------------------------------ [2003-03-25 06:46:39] sniper@php.net What webserver is used? How is PHP configured in it? Are you using CGI binary or a module? What is the diff -u between the php.ini-dist file and your php.ini ? ------------------------------------------------------------------------ [2003-03-25 05:51:58] carl at voodoomedia dot co dot uk I'm afraid that "You're doing something wrong" just isn't an acceptable answer. It's a problem with PHP's session handler or serializer for sure. I can replicate it by using this script <?php session_start(); if (!isset($_SESSION['tempVal'])) $_SESSION['tempVal'] = 0; $_SESSION['tempVal']++; echo 'session val is now '.$_SESSION['tempVal'].'<BR>'; echo '<A HREF="sesstest.php">click here to reload</A> ?> If I call that page from an automated page refresh script that I have at some point within an hour I will get [25-Mar-2003 11:37:27] PHP Fatal error: Maximum execution time of 40 seconds exceeded in e:\www\sesstest.php on line 2. ------------------------------------------------------------------------ [2003-03-18 11:38:50] sniper@php.net You're doing something wrong, ask support questions on the mailing lists. ------------------------------------------------------------------------ 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/22747 -- Edit this bug report at http://bugs.php.net/?id=22747&edit=1