[ 
https://issues.apache.org/jira/browse/QPID-8232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704940#comment-16704940
 ] 

ASF subversion and git services commented on QPID-8232:
-------------------------------------------------------

Commit 2eb9c74e02a737d177da540029423e65397f2764 in qpid-broker-j's branch 
refs/heads/7.0.x from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=2eb9c74 ]

QPID-8232: [Broker-J] Support ability to turn off logger

(cherry picked from commit 367b0805cba347a362a143da4948704f6d263118)


> [Broker-J] Disabling logging using  log level OFF is not respected by the 
> logging framework
> -------------------------------------------------------------------------------------------
>
>                 Key: QPID-8232
>                 URL: https://issues.apache.org/jira/browse/QPID-8232
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Broker-J
>    Affects Versions: qpid-java-broker-7.0.6
>            Reporter: Alex Rudyy
>            Assignee: Alex Rudyy
>            Priority: Major
>             Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.7
>
>         Attachments: 
> 0003-QPID-8232-Broker-J-Optimise-logging-with-LoggerNameA.patch
>
>
> When two logging rules created where one rule allows logging  for the given 
> hierarchy and another rule disables specific logging for the logger from the 
> hierarchy declared in the first rule, the rule disabling the logging should 
> take precedence.
> For example, when the one rule allows 'info' logging for loggers matching 
> "qpid.message.*" and another rule is added to turn off logging of log event 
> from logger "qpid.message.exchange.discardmsg", the logs from logger 
> "qpid.message.exchange.discardmsg" should not be appended. The current 
> implementation allows logging from disabled loggers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to