What is the two year old problem?
Win64 Server 2008 and SocketException Invalid argument
Same SocketException error as above. May or may not be related to our new origin issue. Just saying that it shows in the logs and in our new edge servers which were recently installed with Win Server 2008 64-bit.
We use StartupStreams.xml and most times, all our streams from origin to edge start okay on the edge. Sometimes they don’t and then takes random number of retries, walking up the free socket list. Occasionally one or two never start and we have to reboot. We don’t reset the edge servers too often so it’s manageable. We run the origin to edge streams 24/7 and once started successfully… don’t have a problem.
When we reported two years ago, we took the discussion offline and both you and Charlie punted on a solution. So we switched DC’s and went all 32-bit until last month.
Our new origin should really be a 64-bit environment too but we were scared about running into this issue in a more critical place. Seems we may have hit it anyway.
It should not be happening on any OS-Wowza combination.