Hi Alex,
Thanks for providing the patch. I verified the fix with same perf test, and
it does prevent broker from going OOM, however. DM utilization doesn't get
any better after hitting the threshold (where flow to disk is activated
based on total used % across broker - graph in the link below).
A
Hi all,
I am trying to create a queue with a message limit of 1, but the broker
does not seem to be enforcing the limit.
Repro steps:
1. $ qpidd --auth=no # start the cpp broker
2. $ python qmf-test.py # creates a ring queue with max-queue-count=1 and
send 2 messages
3. $ qpid-stat -q
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
On 05/05/17 09:40, Jiri Danek wrote:
So here is fixed video which shows it working properly:
https://youtu.be/uq0BGYvwMkg
Very nice!
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail:
On Fri, May 5, 2017 at 10:12 AM, Gordon Sim wrote:
>
> A proton container instance is not threadsafe, so all calls to it and the
> connections it manages should be done on the containers event thread (i.e.
> the one calling run).
>
> You can trigger a custom 'event' to be handled on the container
On 05/05/17 08:53, Jiri Danek wrote:
Hello the list,
I want to ask for help with my application. It is a rather trivial group
chat written in Python using the Python Qpid Proton library and the Tkinter
library for GUI.
I have two problems regarding this application.
First, I want to ask if I d
Hello the list,
I want to ask for help with my application. It is a rather trivial group
chat written in Python using the Python Qpid Proton library and the Tkinter
library for GUI.
I have two problems regarding this application.
First, I want to ask if I designed it correctly. I am spawning two
10 matches
Mail list logo
