#47314 [NoF->Opn]: SoapClient leave tcp connections in "time_wait"

ID: 47314 User updated by: bernd dot ott at k-m dot info Reported By: bernd dot ott at k-m dot info -Status: No Feedback +Status: Open Bug Type: SOAP related Operating System: Windows PHP Version: 5.2CVS-2009-02-05 (snap) Assigned To: dmitry New Comment: "No feedback was provided" is not correct. Previous Comments: ------------------------------------------------------------------------ [2009-03-03 01:00:01] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2009-03-02 08:34:22] bernd dot ott at k-m dot info i created the sample on a old xp machine with apache 2.2 installed. i have tested the webservice with different Clients made with different languages. no other client keep the connections in "time_wait". ------------------------------------------------------------------------ [2009-02-23 11:21:16] pajoye@php.net Do you have IPv6 installed (by default on Vista or later, needs an extra package for XP/2k). If yes, edit: C:\windows\system32\drivers\etc\hosts and comment the following line: ::1 localhost becomes: #::1 localhost Restart the web server and test again. ------------------------------------------------------------------------ [2009-02-23 11:11:00] bernd dot ott at k-m dot info open the socket with fsocketopen / fclose doesnt leave timewait connections. the problem is, this causes my .net soap server to a not response state. this is because all workers are allocated. i cant use keep alive, my page is using ajax to a php page which contains the soapclient. ------------------------------------------------------------------------ [2009-02-18 15:41:39] dmitry@php.net According to http://tangentsoft.net/wskfaq/articles/debugging-tcp.html and http://www.developerweb.net/forum/showthread.php?t=2941 it's a normal TCP behaviour. (In case you run Apache benchmark you can see a lot of connections in TCP_WAIT state too) In case you call SOAP functions on the same SoapClient object and your Web Server responds with keep-alive HTTP header all the functions will use a single TCP connection. ------------------------------------------------------------------------ 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/47314 -- Edit this bug report at http://bugs.php.net/?id=47314&edit=1