Posted by Jim Guerber on November 06, 2007 at 15:32:23:
We may have some light at the end of this tunnel. As you know I opened an incident with Microsoft relating to this problem. We found a willing customer to monitor using tools provided by Microsoft. Software monitoring began one week ago. We saw approximately 2 of these disconnect incidents a day last week.
I also contracted with the programmer who first built the TCP/IP framework on which CfamNetServe was built. After looking at our code he suggested we update to the latest version of his framework. This was not a trivial task, but Brian spent much of the weekend doing just that.
We installed the new CfamNetServe on the test account Sunday night.
It has been almost 2 full days since, and we have seen NO PROBLEM yet.
Keep your fingers crossed. If this holds up, we will have a new server release out on Friday.
for your information, here is the text of the communication from the author of the framework:
"Guys,
I've spent a couple of hours looking at the code this evening. I'd quite like you to finish switching to using the latest version of the code (which, I think, Brian is in the process of doing now) before I spend any more time looking at your code as this could fix your problems.
The issues that you're experiencing could be due to how the old version of the framework dealt with connection errors coming out of the IOCP. For the errors that were assumed to be fatal (which, in that version, were too numerous) the exception thrown would destroy an I/O pool thread and that would cause outstanding I/O requests that were issued by that thread (on any connection) to be aborted. The latest free code deals with these errors better and could potentially fix your problems. As for why you're suddenly having these problems on some machines, I think it would be cheapest for you to try the latest free version and then if that still gives problems I'll take another, more detailed, look.
Len"