Since my last post, we have done a number of tests involving some
combinations of the following changes to determine which is more helpful in
alleviating this issue:
1. Increasing the buffer count from 4 to 8;
2. Reducing the receiver capacity from 100 to 10;
3. Upgrading from Windows Server 2003
Hi Jakub,
Thank you for investigation and keeping the thread alive. I hope we will get
to a conclusion soon about how to fix this.
-
Best Regards,
Hamid.
--
View this message in context:
One more update from my side ... I finally managed to build the 0.22
release. The problem is fully reproducible there as well. However, I tried
to increase the BufferCount value in AsynchIO.h from 4 to 5 and that seems
to solve the problem - at least in the terms that the error doesn't
reproduce
Hi Jakub,
It is really good to know that increasing the BufferCount value to 5 helps
to resolve the problem.
Should we double the BufferCount from 4 to 8 instead? Or do you thing there
any be any negative effects of doing this?
Thanks
-
Best Regards,
Hamid.
--
View this message in
Hi Hamid,
I'm sorry, I do not really know the idea behind the buffers. Steve
mentioned the possibility of increasing the buffer count. From the code
where the exception is created it is apparent that there is additional
buffer missing, but I do not really know how the SSL data are decrypted and
Hi all,
This issue doesn't seem to be so complicated to reproduce. I used a
following scenario:
1) Create a large queue on a broker (C++ / Linux)
2) Start feeding messages into the queue using C++/Linux program (in my
case I used approximately 1kB messages)
3) Connect with a receiver
Hi,
1. So, do anyone have any recommendation on how we can allocate more buffer
space programmatically to avoid this problem?
2. Could the exception in theory have caused the connection issues that I
mentioned in the Windows build?
Thanks,
Jin-Ghee Lu (Gene)
--
View this message in context:
Hi Gene,
Apologies for the delay.
1. So, do anyone have any recommendation on how we can allocate more
buffer space programmatically to avoid this problem?
You can't. You could try increasing BufferCount in
qpid/cpp/src/qpid/sys/AsynchIO.h and rebuilding but I don't think that's a real
Hi Steve,
Thank you very much for your response. As I mentioned before, we have not
seen the issue in our in-house tests. But I will try to come up with some
test cases to reproduce the issue.
Thanks again,
Gene
--
View this message in context:
Unfortunately, we have only seen this issue in our production environment,
where there are large amount of incoming messages from the broker. If we
can reliably reproduce the issue, I will raise a JIRA. Some follow-up
questions:
1. Can we allocate more buffer space ourselves programmatically?
-Original Message-
From: jglu2000 [mailto:jinghe...@hotmail.com]
Sent: Wednesday, May 15, 2013 11:54 AM
To: users@qpid.apache.org
Subject: Qpid throwed WSAENOBUFS while receiving data from a broker
We have a Windows Qpid 0.20 C++ client that receives huge amount of data
from a
11 matches
Mail list logo
