Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.2.2

Bug #17484 PHP Fatal error: Maximum execution time of 30 seconds exceeded
Submitted: 2010-06-11 17:25 UTC
From: hm2k Assigned: ashnazg
Status: Closed Package: Net_Socket (version 1.0.9)
PHP Version: 5.3.2 OS:
Roadmaps: (Not assigned)    
Subscription  


 [2010-06-11 17:25 UTC] hm2k (James Wade)
Description: ------------ I'm using Net_Whois (SVN) which uses this module. I've set the timeout as 6 seconds, yet I am seeing the following error: PHP Fatal error: Maximum execution time of 30 seconds exceeded in /usr/lib/php/Net/Socket.php on line 514 The script shouldn't run longer than the timeout. Test script: --------------- Any sockets script will do, it's difficult to reproduce as it doesn't always occur. It appears to be an issue with the readAll() function which doesn't timeout. it seems that it will continue to read the socket indefinitely. Expected result: ---------------- [Return false if timeout exceeded] Actual result: -------------- PHP Fatal error: Maximum execution time of 30 seconds exceeded in /usr/lib/php/Net/Socket.php on line 514

Comments

 [2010-10-21 16:59 UTC] hm2k (James Wade)
There needs to be a way to timeout the socket connection if it takes longer than the timeout.
 [2013-05-15 15:53 UTC] alec (Aleksander Machniak)
How do you set the timeout? It might be a duplicate of https://pear.php.net/bugs/bug.php?id=18437
 [2017-02-06 12:57 UTC] alec (Aleksander Machniak)
-Status: Open +Status: Feedback
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.php.net/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to "Open". Thank you for your interest in PEAR.
 [2017-03-08 19:00 UTC] ashnazg (Chuck Burgess)
-Status: Feedback +Status: No Feedback
 [2017-03-08 19:07 UTC] ashnazg (Chuck Burgess)
-Status: No Feedback +Status: Closed -Assigned To: +Assigned To: ashnazg
Fix included in upcoming v1.1.0 release.