We have been trying to perform in-house tests in a more controlled testing
environment (so that we can run debugger and other tools) to reproduce this
issue with no luck.  But we are continuously getting reports from our
production environment.  One reason we think the issue is happening more
frequent in production is that we have a lot of incoming messages from the
brokers (external to us at a different institution).  Some information about
our configurations and patterns we have seen in production after enabling
the DEBUG+ logging for Qpid:

- Windows Server 2003
- Qpid 0.20 build on Windows / Visual C++ 2010
- SSL enabled with client/server certificates
- Made changes based on https://issues.apache.org/jira/browse/QPID-3914 to
resolve client certificate authentication issue in Windows
- Our Windows client has been set up to have 3 client queues to receive
incoming messages from brokers, with capacities set to 100.  One of the
queues is busier than the other two, with continuous downloads coming from
the brokers.
- The busy queue could see as many as 100 messages per second being
"delivered" or "pushed".
- Prior to the exception, we usually saw a lot more "pushed" than
"delivered".

We had speculated that maybe our thread that is responsible for fetching had
stopped fetching or receiving, and we had tried to simulate that by not
fetching / receiving.  But Qpid would simply signal the brokers to stop
sending, and no exception was observed.

We were hesitant to put in the BufferCount changes without knowing more. 
But given the circumstance, we will give it a try.  Will update this post
one way or another.

Thanks,
Jin-Ghee Lu (Gene)








--
View this message in context: 
http://qpid.2158936.n2.nabble.com/Qpid-throwed-WSAENOBUFS-while-receiving-data-from-a-broker-tp7592938p7595892.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Reply via email to