socket timeout being ignored

[yawnmoth]

Say I have the following script:

<?
$timeout = 5;
$start = time();
$fsock = fsockopen('125. 1.119.10',80,$e rrno,$errstr,$t imeout);

// reduce $timeout by the amount of time that it took for fsockopen to
connect.
$timeout-=(time()-$start);

socket_set_time out($fsock,$tim eout);

fputs($fsock,"G ET http://www.google.com/ HTTP/1.0\r\n");
fputs($fsock,"H ost: www.google.com\ r\n\r\n");

while ( !feof($fsock) )
{
echo fgets($fsock);
}

fclose($fsock);
?>

As you can tell, the timeout is set to 5 seconds in fsockopen and then
is set to how ever many seconds out of that 5 that fsockopen didn't
take to connect.

All in all, the whole script should run in, at most, 5 seconds. Or
atleast it seems like it should. Sometimes, however, it doesn't - it
takes several minutes. And unfortunately, this happens enough times to
be kinda a nuisance. And I have no idea what the problem is.

Any ideas?

[Jerry Stuckle]

yawnmoth wrote:

Say I have the following script:

<?
$timeout = 5;
$start = time();
$fsock = fsockopen('125. 1.119.10',80,$e rrno,$errstr,$t imeout);

// reduce $timeout by the amount of time that it took for fsockopen to
connect.
$timeout-=(time()-$start);

socket_set_time out($fsock,$tim eout);

fputs($fsock,"G ET http://www.google.com/ HTTP/1.0\r\n");
fputs($fsock,"H ost: www.google.com\ r\n\r\n");

while ( !feof($fsock) )
{
echo fgets($fsock);
}

fclose($fsock);
?>

As you can tell, the timeout is set to 5 seconds in fsockopen and then
is set to how ever many seconds out of that 5 that fsockopen didn't
take to connect.

All in all, the whole script should run in, at most, 5 seconds. Or
atleast it seems like it should. Sometimes, however, it doesn't - it
takes several minutes. And unfortunately, this happens enough times to
be kinda a nuisance. And I have no idea what the problem is.

Any ideas?

What happens if the fsockopen() takes longer than 5 seconds?

See the note on fsockopen() - the timeout may not be available in all
environments. So a delay due to routing, server load or whatever may
cause the open to take longer than 5 seconds, putting a negative value
in your $timeout. I don't know what PHP will do with a negative value -
maybe convert it to a very large positive value?

Additionally, the timeout restarts every time you go a fgets(). The
server could be sending one line every 4 seconds, for instance. 10
lines would be 40 seconds with no errors.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[yawnmoth]

Jerry Stuckle wrote:

yawnmoth wrote:
<snip>

What happens if the fsockopen() takes longer than 5 seconds?

See the note on fsockopen() - the timeout may not be available in all
environments. So a delay due to routing, server load or whatever may
cause the open to take longer than 5 seconds, putting a negative value
in your $timeout. I don't know what PHP will do with a negative value -
maybe convert it to a very large positive value?

That's a good point - it's been fixed :)

Additionally, the timeout restarts every time you go a fgets(). The
server could be sending one line every 4 seconds, for instance. 10
lines would be 40 seconds with no errors.

So I guess I should just use fread with as big a number as possible?
Like pow(2,20) or something?

The fact that fgets (and fread), though, can return empty lines, even
when they're in blocking mode, makes me think that this wouldn't work?
(I made another post about this)

[Jerry Stuckle]

yawnmoth wrote:

Jerry Stuckle wrote:

>>yawnmoth wrote:
<snip>

What happens if the fsockopen() takes longer than 5 seconds?

See the note on fsockopen() - the timeout may not be available in all
environment s. So a delay due to routing, server load or whatever may
cause the open to take longer than 5 seconds, putting a negative value
in your $timeout. I don't know what PHP will do with a negative value -
maybe convert it to a very large positive value?

That's a good point - it's been fixed :)

>>Additionall y, the timeout restarts every time you go a fgets(). The
server could be sending one line every 4 seconds, for instance. 10
lines would be 40 seconds with no errors.

So I guess I should just use fread with as big a number as possible?
Like pow(2,20) or something?

The fact that fgets (and fread), though, can return empty lines, even
when they're in blocking mode, makes me think that this wouldn't work?
(I made another post about this)

Could be. I haven't seen that occur, but there could be a bug in it.
You could try a big fread() call. Don't know what it will do. I
haven't used the timeout parm like that. Normally I want to get the
results even if it takes a few second.
--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[yawnmoth]

Jerry Stuckle wrote:

yawnmoth wrote:
<snip>
Could be. I haven't seen that occur, but there could be a bug in it.
You could try a big fread() call. Don't know what it will do. I
haven't used the timeout parm like that. Normally I want to get the
results even if it takes a few second.

I actually would like to get the results, too - just not at the cost of
a few minutes, heh.

[Jerry Stuckle]

yawnmoth wrote:

Jerry Stuckle wrote:

>>yawnmoth wrote:
<snip>
Could be. I haven't seen that occur, but there could be a bug in it.
You could try a big fread() call. Don't know what it will do. I
haven't used the timeout parm like that. Normally I want to get the
results even if it takes a few second.

I actually would like to get the results, too - just not at the cost of
a few minutes, heh.

In that case I would suggest trying to track down the source of the problem.

If the socket opens OK, you have a connection to the server (what is
this server, anyway - I don't get a response at that IP). It shouldn't
take Google too long to respond since you're not searching. In this
case an IP trace might help.

Another alternative, BTW, to stop processing, would be to check the time
in your loop rather than wait for the timeout. If processing exceeds 5
seconds, stop. For instance:

$timeout = 5;
$start = time();
$fsock = fsockopen('125. 1.119.10',80,$e rrno,$errstr,$t imeout);

socket_set_time out($fsock,$tim eout);

fputs($fsock,"G ET http://www.google.com/ HTTP/1.0\r\n");
fputs($fsock,"H ost: www.google.com\ r\n\r\n");

while ( !feof($fsock) && time() < ($start + $timeout))
{
echo fgets($fsock);
}

fclose($fsock);

This should terminate loop processing as soon as it returns from the
fgets() and you've exceeded you 5 second timeout.

It might allow you to see what you're getting and help track down the
problem.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===