I have put a change in via
https://issues.apache.org/jira/browse/QPIDJMS-292 to address it. If
you want to give it a try you can either check out the code (mirrored
at https://github.com/apache/qpid-jms), or grab the latest
0.23.0-SNAPSHOT from
https://repository.apache.org/content/repositories/sna
Will you let me know if a Jira ticket is made as a result of this so I can
track which version gets an adjustment?
I did more testing around this and am convinced this is what caused our
Broker to get a Out Of Memory for Direct Memory. We saw our broker crashing
and our primary client of the large
Thanks for the replies and the work around. Getting this working will be
great as we mostly use the competing consumer approach here. When
somebodies queue gets backed up to half a million messages they want to
just scale out their instances in CloudFoundry to increase throughput.
On Fri, May 5, 20
On 5 May 2017 at 14:14, Robbie Gemmell wrote:
> I can also reproduce this. I believe it is a deficiency in how/when
> the client handles granting more link credit, and it will show
> particularly badly in the scenario described where the broker is able
> to significantly/totally use the existing
I can also reproduce this. I believe it is a deficiency in how/when
the client handles granting more link credit, and it will show
particularly badly in the scenario described where the broker is able
to significantly/totally use the existing credit between processing of
individual messages and the
Hi Dan
Thanks for the comprehensive report. I can reproduce what you see and
confirm there appears to be a bug. I'll hope to be able to take a
closer look later today or Monday and get back to you with more
information.
Keith.
On 4 May 2017 at 23:39, Dan Langford wrote:
> So over the past few
So over the past few weeks we have had a huge influx of messages on our
enterprise message bus (qpid java 6.0.4 serves the AMQP1.0 messaging
portion) and when one of our clients struggled scaling their application up
it got us looking at prefetch. we thought it was odd that all 500k messages
in the
