Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
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
-
None
Description
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.
Attachments
Issue Links
- is cloned by
-
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
- Closed