qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-8017) [Broker-J] [BDB] JE log events written at JUL level FINE and below not included in the log produced by a BrokerLogger
Date Mon, 13 Nov 2017 16:09:00 GMT

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

Keith Wall commented on QPID-8017:

The existence of both Broker and VirtualHostInclusionRules make propagating the level to the
JUL hierarchy slightly tricky.  A correct implementation would need to resolve the lowest
level if broker/virtualhost inclusion rules were configured differently.  Also if an inclusion
rule were removed, it would be necessary to propagate the level resulting from the remaining
inclusion rules. 

> [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
>             Fix For: Future
> 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
> 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

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

View raw message