Alan Conway created QPID-6012:
---------------------------------

             Summary: HA fix ACL notice log message about accounting for TX 
queues.
                 Key: QPID-6012
                 URL: https://issues.apache.org/jira/browse/QPID-6012
             Project: Qpid
          Issue Type: Bug
          Components: C++ Clustering
    Affects Versions: 0.28
            Reporter: Alan Conway
            Assignee: Alan Conway


HA module creates temporary TX queues but does not go thru the  ACL accounting 
code. This causes N+1 notice log messages from ACL module for every N 
transactions. Its an old bug but was exposed by recent changes to ACL logic. 
The fix is trivial & low risk, there are no functional changes, but without the 
fix the log files are extremely cluttered with notice level (highest below 
warn) scary looking log messages.

Steps to Reproduce:

Start a HA cluster with >1 member

qpid-send --tx 1 -a 'qq;{create:always}' -b localhost:6000

Actual results:

Primary broker log contains
2014-08-15 11:19:27 [Security] notice ACL resource counter: Queue 
'qpid.ha-tx:3ba46af9-e37c-40f1-ae7f-1bdd8fdf19ea' not found in queue owner map
2014-08-15 11:19:27 [Security] notice ACL resource counter: Queue 
'qpid.ha-tx:2e2de2d4-d7b0-48b5-8fac-7f2680916106' not found in queue owner map
2014-08-15 11:19:27 [Security] notice ACL resource counter: Queue 
'qpid.ha-tx:230050dd-28cf-4f09-a096-7df7ab404c7f' not found in queue owner map
2014-08-15 11:19:34 [Security] notice ACL resource counter: Queue 
'qpid.ha-tx:a899c2fb-6be3-4e34-a9a5-16ab2f22d625' not found in queue owner map
2014-08-15 11:19:34 [Security] notice ACL resource counter: Queue 
'qpid.ha-tx:c2a0d1b0-e355-4c76-a0b9-d7dcdb0f7479' not found in queue owner map
2014-08-15 11:19:34 [Security] notice ACL resource counter: Queue 
'qpid.ha-tx:b9ecb26c-94cb-453b-9e18-da377d7d6587' not found in queue owner map


Expected results:

No ACL related messages

Additional info:
[reply] [−]  Private Comment 1



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to