Re: WSAENOBUFS on winsock client application

Hi Friedhelm,
From my research, there are two known issues regarding the error message. I
would like to post some articles here for your reference:
You receive an error message when you run a custom Winsock network program
on a Microsoft Windows XP Service Pack 2-based computer
http://support.microsoft.com/default.aspx?scid=kb;EN-US;905628

When you try to connect from TCP ports greater than 5000 you receive the
error 'WSAENOBUFS (10055)'
http://support.microsoft.com/default.aspx?scid=kb;EN-US;196271

You can also use TCPView to monitor how many TCP connections opened in your
process when this issue happens:
TCPView for Windows v2.51
http://www.microsoft.com/technet/sysinternals/Networking/TcpView.mspx

Note that since this issue is environment specific, to track the root cause
of this issue, dump analysis would be required, however this work need your
contacting Microsoft Customer Support Services (CSS). If our suggestions
here do not help you on resolving this issue, effectively and immediately I
recommend that you make a call to CSS so that a more dedicated support
professional will assist you further. Please be advised that contacting
phone support will be a charged call.

To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.

Appreciate your understanding on this. If you have any other questions or
concerns, please feel free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================


"FriedhelmEichin" <FriedhelmEichin@xxxxxxxxxxxxxxxx> wrote in message
news:CCF10470-22F7-4793-B793-644A97BFF1EF@xxxxxxxxxxxxxxxx
I'd guess that it's more likely to be a bug in the way the code
handle's the unexpected connection termination which possibly results
in some corruption somewhere. Or just broken error handling?

Yes, that might be possible, of course. The way handling an unexpected
connection closure (caused by the server or network) is as follows :

1. receiving error on pending I/O-Operation (WSARecv or WSASend) or
receiving an FD_CLOSE event.
2. call WSASendDisconnect(...)
3. wait for termination of pending I/O operation, if any.
4. activate the DONTLINGER Option using setsockopt
5. call closesocket

any idea what might be wrong ?

--
best regards
friedhelm


"Len Holgate" wrote:

It doesnt really make sense that it's just ONE connection having this
problem though, does it? Surely if Winsock was experiencing a low
resource situation you'd get WSAENOBUFS occurring on lots of
operations on various open sockets, rather than just on the one?

I've seen this a lot under real low resource situations, see here for
more details:
http://www.lenholgate.com/archives/000580.html
http://www.lenholgate.com/archives/000564.html
and things that these blog posts link to...

I'd guess that it's more likely to be a bug in the way the code
handle's the unexpected connection termination which possibly results
in some corruption somewhere. Or just broken error handling?

As an aside, I thought that WSAENOBUFS was related to non-paged pool
or locked pages limits than simple memory allocation?

Len Holgate
http://www.lenholgate.com
Free C++ IOCP server framework available here:
http://www.lenholgate.com/archives/000637.html






.

Relevant Pages