[
https://issues.apache.org/jira/browse/QPID-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249418#comment-16249418
]
Alex Rudyy edited comment on QPID-8017 at 11/13/17 11:28 AM:
-------------------------------------------------------------
Keith's idea about propagation of log level configuration into JUL logger looks
like a reasonable one. It is essentially what
[LevelChangePropagator|https://logback.qos.ch/xref/ch/qos/logback/classic/jul/LevelChangePropagator.html]
does but we would need to have the logic implemented in {{InclusionRule}}s. I
think we can add an attribute for the rule like "propagateIntoJUL" where on
rule opening we would set the JUL log level as suggested by Keith
if"propagateIntoJUL" is true. We would need to keep a reference to JUL logger
in internal map in order to prevent it garbage collection.
was (Author: alex.rufous):
Keith's idea about propagation of log level configuration into JUL logger looks
like a reasonable one. It is essentially what
[LevelChangePropagator|https://logback.qos.ch/xref/ch/qos/logback/classic/jul/LevelChangePropagator.html]
does but we would need to have the logic implemented in [[InclusionRule]]s. I
think we can add an attribute for the rule like "propagateIntoJUL" where on
rule opening we would set the JUL log level as suggested by Keith
if"propagateIntoJUL" is true.
> [Broker-J] [BDB] JE log events written at JUL level FINE and below not
> included in the log produced by a BrokerLogger
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-8017
> URL: https://issues.apache.org/jira/browse/QPID-8017
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.1, qpid-java-broker-7.0.0
> Reporter: Keith Wall
> Priority: Minor
>
> Reproduction:
> * Add {{NameAndLevel}} logger inclusion rule BrokerLogger {{file}} for source
> {{com.sleepycat.je.*}} with Level.ALL
> * Add a BDB HA VHN/VHN
> * Expected behaviour: verbose logging from JE. Actual behaviour: moderate
> logging only
> For instance, JE writes the following message at {{FINE}} which should be
> logged by the handler as {{TRACE}} but it is absent.
> {noformat}
> 2017-11-07 10:42:15,467 TRACE [Cleaner-1] (c.s.j.c.UtilizationCalculator) -
> [default] Clean file none: predicted min util is below minUtilization,
> current util min: 20 max: 20, predicted util min: 20 max: 20
> {noformat}
> There is a workaround for the functional problem, albeit a restart is
> required and the ability to change the process's system properties. Use the
> normal JUL system property {{java.util.logging.config.file}}. Set this to
> the location of a logging.properties file with the {{com.sleepycat.je}}
> logger set to the desired level. Once the JVM is restarted, the Broker's log
> files will include the logging.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
