[
https://issues.apache.org/jira/browse/QPID-7890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138264#comment-16138264
]
Robbie Gemmell commented on QPID-7890:
--------------------------------------
Questions should generally go to the users@ mailing list.
I noticed that [~chug] said the following last week in a reply to the
notification mails that go to the dev@ mailing list, which you might not have
seen as a result:
{quote}
Try enabling logging in the qpidd command line:
--log-enable debug+:Security
That should expose the acl policy logic that arrives at the connection
allow/deny conclusions.
{quote}
> Qpid C++ Broker 1.36 Max Connections Per User Option not working
> ----------------------------------------------------------------
>
> Key: QPID-7890
> URL: https://issues.apache.org/jira/browse/QPID-7890
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: qpid-cpp-1.36.0
> Environment: Windows 10 64-Bit, Qpid C++ Broker 1.36
> Reporter: Spud Strumpet
>
> I have been trying to configure the maximum connections per user but none of
> the options seem to be having an affect.
> I have tried various combinations of setting:
> * --connection-limit-per-user N on the command line, and
> * quota connections N username in the acl file
> In the broker trace log, it confirms that the connection limit is enabled,
> but all connections then succeed anyway. None are rejected.
> I have tried setting max connections to zero in both places for all users,
> but still I can connect.
> Is anyone able to confirm that the max connections options are working as
> expected in the C++ 1.36 Broker? Thanks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
