Hello Pat,
What components are you using?
C++ broker, Java Broker?
Which client?
You said "The broker had flow control thresholds set accordingly". Can
you elaborate what exactly you did?
Kind regards,
Lorenz
On 31/01/17 00:24, Demoss, Patrick wrote:
I was surprised to see certain behavior while I was implementing a basic flow
control broker.
I created a sender that sent lots of messages to the broker, letting the queue
stack up. There was no receiver to take messages off the queue.
The broker had flow control thresholds set accordingly, and I expected the stop
threshold to trigger and the sender to be blocked. But it was never blocked,
rather the queue grew to an enormous size until I manually killed it.
Is this proper behavior for flow control? Because I would have expected to
trigger in a basic case like this. What's the purpose of flow control if it
doesn't guard against this type of situation?
Pat
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
