You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (Jira)" <ji...@apache.org> on 2020/09/19 17:49:00 UTC

[jira] [Resolved] (QPID-8429) [Broker-J] [7.1.x] The outcome of logging rule for the exact logger could be superseded by the rule for logger with a trailing wild card

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

Alex Rudyy resolved QPID-8429.
------------------------------
    Resolution: Fixed

> [Broker-J] [7.1.x] The outcome of logging rule for the exact logger could be superseded by the rule for logger with a trailing wild card
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-8429
>                 URL: https://issues.apache.org/jira/browse/QPID-8429
>             Project: Qpid
>          Issue Type: Bug
>          Components: Broker-J
>    Affects Versions: qpid-java-6.1.6, qpid-java-broker-7.0.3, qpid-java-broker-7.0.2, qpid-java-6.0, qpid-java-6.0.1, qpid-java-6.0.2, qpid-java-6.0.3, qpid-java-6.0.4, qpid-java-6.0.5, qpid-java-6.1, qpid-java-6.0.6, qpid-java-6.1.1, qpid-java-6.1.2, qpid-java-6.0.7, qpid-java-6.1.3, qpid-java-6.0.8, qpid-java-6.1.4, qpid-java-broker-7.0.0, qpid-java-6.1.5, qpid-java-broker-7.0.1, qpid-java-6.1.7, qpid-java-broker-7.1.0, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, qpid-java-broker-7.0.6, qpid-java-broker-7.0.7, qpid-java-broker-7.1.1, qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3, qpid-java-broker-7.1.4, qpid-java-broker-7.1.5, qpid-java-broker-7.1.6, qpid-java-broker-7.1.7, qpid-java-broker-7.1.8
>            Reporter: Alex Rudyy
>            Assignee: Alex Rudyy
>            Priority: Major
>             Fix For: qpid-java-broker-7.1.9
>
>
> The logging rule with an exact logger name  can be ignored if there is a rule where logger is specified with a trailing wild card and that logger name pattern matches the name of the exact logger name.
> For example, if the logging rule for the logger {{org.apache.qpid.foo.*}} is configured with a log level {{INFO}} and there is another rule for the logger {{org.apache.qpid.foo.bar}} configured with a log level {{WARN}}, the {{INFO}} log records from logger {{org.apache.qpid.foo.bar}} are got appended into the logs.
> It is expected that  outcome for the rule with the  exact logger name {{org.apache.qpid.foo.bar}} should supersede the outcome of the rule with logger having wildcards {{org.apache.qpid.foo.*}}. Thus, only log records  with log level {{WARN}} and {{ERROR}} which are produced by logger {{org.apache.qpid.foo.bar}}   should be appended to the logs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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