Hi,
I played a bit with the quotas for connections and queues in the ACL files.
It seems, that when I configure a quota for one user, the broker
automatically adds a quotas for all other users which are set to 0.
For example, after adding the rule with connection quota for user1:
quota
Hi Jakub,
Referring to
http://qpid.apache.org/releases/qpid-0.22/cpp-broker/book/chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-Authorization-Specifying_ACL_Quotas.
This document describes how the quotas work and some more subtle issues that
arise when an ACL file is
Hi Chuck,
I see following situations (0.24 RC1), where the second doesn't work.
a)
- Configuration:
I use only the command line options (which are supposed to mean
unlimited):
connection-limit-per-user=0
connection-limit-per-ip=0
max-queues-per-user=0
- Expected result:
I can create unlimited
On 08/08/2013 05:46 PM, Jakub Scholz wrote:
Are these AMQP 1.0 related changes documented somewhere?
Not properly yet. I've been sending out some rough notes to the user
list (updated version attached). I need to spend some time figuring out
where and how to make the information more
Hi Jakub,
The doc tries to explain:
Per-user connection quotas are disabled when two conditions are true: 1) No
--connection-limit-per-user command line switch and 2) No quota connections
rules in the ACL file.
If your command line specified zero and you had no ACL settings then the zero
If you want to work with AMQP 0-10, and not AMQP 1.0, you don't need to worry
about missing qpid-proton. Similarly, the missing python and perl libs keep you
from building those bindings. If you don't need to program qpid with
python/perl, you don't need to worry about those.
For ha, if you do
