--- In hercules-390@yahoogroups.com <mailto:hercules-390%40yahoogroups.com>
, "Fish" <fish@...> wrote:
>
> "TcpTimedWaitDelay "
>
> Valid Range: 30-300 (decimal)

> Try changing your
> "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> \TcpTimedWaitDelay" value to something like 1 or 2 seconds (just
> while we're testing) and then try your test (fishbug) again.

Ok, I don't have this variable. I could add it
though, but I've not done that before, and I
don't want to reboot right now anyway.

Secondly, the minimum is 30 seconds. I am
reluctant to find out what happens when I do
something that is documented as being wrong.
I have enough trouble with my computer even
when I'm doing everything by the book.

Thirdly, can't I simply wait for the default
time and then try again? I've just tried again
after being at work all day and got the same
result.

BFN. Paul.

**************************

From Fish >> (Previous email)

If that helps, all we might need to do to fix the problem might be
something as simple as adding a 'setsockopt' call (after the 'bind')
to enable the SO_REUSEADDR option. <shrug>

>> Actually Fish has a great idea.

I have written a simple windows socket server that used the
Automatic anonymous port feature that we are using here.

I never thought about the fact that "the system assigned port"
Might still be in a un-usable state. This is a very real possibility.

I can not imagine the herc would cycle thru port # quick enough
To wrap around itto a re-use condition.

I was responsible for a tcp server on an ibm mainframe using the sas/c
Bsd/socket library. We used our own well-known port #. But we used
To hit the re-use problem all the time, because in development work
You have to re-cycle the server often. The easy fix was to add the
Re-use address option.

I think adding this will not hurt anything and it could solve some
Of our strange intermitent failure problems. We should add it
To fishbug and see if it fixes the problem on Pauls system :)