Bug #15040 Updated: Socket

From: Date: Wed, 12 Jun 2002 05:00:07 +0000
Subject: Bug #15040 Updated: Socket
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-10207@lists.php.net to get a copy of this message
ID: 15040 Updated by: php-bugs@lists.php.net Reported By: webmaster@weathermetrics.com -Status: Feedback +Status: No Feedback Bug Type: Sockets related Operating System: Windows NT 4.0 PHP Version: 4.1.1 New Comment: No feedback was provided for this bug for over a month, 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". Previous Comments: ------------------------------------------------------------------------ [2002-05-11 18:51:58] mfischer@php.net There have been quite some changes to the sockets extension lately. Please test the upcomming 4.2.1 going to be released in a few days (or test CVS HEAD). ------------------------------------------------------------------------ [2002-01-15 14:38:05] webmaster@weathermetrics.com Ok, here's what MS has to say about what causes that error: WSAECONNRESET (10054) Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket.) This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET. This is what I thought was happening, but why does my script end before my program has time to process it. I should make note that I have one script opening a page with a php script on another webserver and this script is the one that is having problems opening the UDP connection. Could this have anything to do with it. ------------------------------------------------------------------------ [2002-01-15 14:26:20] webmaster@weathermetrics.com It didn't get the second half of my last statement, the fflush DIDN'T work either. This is still an ongoing problem. Thanks, Eric Levy ------------------------------------------------------------------------ [2002-01-15 13:28:16] webmaster@weathermetrics.com I added $w=fflush($fp); after sending the line $w=fputs ($fp, URLUnEncode($Commands["DATA"])); ------------------------------------------------------------------------ [2002-01-15 11:20:34] webmaster@weathermetrics.com I'm sorry I should have made this clear. This was a pre-existing VB App that I have been running for a year now doing the same procedure from embedded clients. It is a possibility I am not fully understanding the life of a PHP socket vs. other socket types. Does anyone have any documentation on the life of a PHP socket. It seems to me like the socket is dyeing before sending the message. Thanks, Eric Levy ------------------------------------------------------------------------ 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/15040 -- Edit this bug report at http://bugs.php.net/?id=15040&edit=1

« previous php.bugs (#10207) next »