#38620 [Fbk->Opn]: curl_multi_* - timeout after 4-6 socket connects on different hosts

ID: 38620 User updated by: tobsn@php.net Reported By: tobsn@php.net -Status: Feedback +Status: Open Bug Type: cURL related Operating System: Debian Sarge PHP Version: 5.1.6 New Comment: because curl_multi is very buggy... give me an example that it is curl... but i dont think so. Previous Comments: ------------------------------------------------------------------------ [2006-09-01 09:37:43] tony2001@php.net And it's not a problem of cURL because .... ? ------------------------------------------------------------------------ [2006-09-01 03:18:19] tobsn@php.net okay, i tried it with the last version (5.1.6) and it does the same... 5/6 connects working the rest brings up a timeout. ------------------------------------------------------------------------ [2006-09-01 02:45:48] tobsn@php.net just try it youself. take the example script and add ~20 urls instead of just 3. and run that in a loop. you will see the first 4, max. 6 connects working and getting a result back. every socket per loop after the 6 working sockets just replying a timeout. ------------------------------------------------------------------------ [2006-09-01 02:41:21] tobsn@php.net because i tested it on 3 different systems each on a different provider. always the same result, in every curl_multi_init the first 4 inits work the rest gets a timeout. to get sure its not a resolving limit or something i put up a test script that i started 20 times at the same time with a small bash script an screen. the 20 scripts using only 4 sockets per perl init. but they working perfectly. makes sure that theres no limit at the provider or on the machines for resolving domains or whatever. so there must be a problem in the curl_multi functions... dont know where or what but it is a bug. ------------------------------------------------------------------------ [2006-08-28 06:47:15] tony2001@php.net And why do you think it's a PHP problem? ------------------------------------------------------------------------ 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/38620 -- Edit this bug report at http://bugs.php.net/?id=38620&edit=1