qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Rudyy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-8232) [Broker-J] Disabling logging using log level OFF is not respected by the logging framework
Date Mon, 10 Sep 2018 12:14:00 GMT

     [ https://issues.apache.org/jira/browse/QPID-8232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alex Rudyy updated QPID-8232:
    Attachment: 0003-QPID-8232-Broker-J-Optimise-logging-with-LoggerNameA.patch

> [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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message