[
https://issues.apache.org/jira/browse/QPID-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-8017:
-----------------------------
Description:
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.
was:
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 problem, using the traditional JUL system
property {{java.util.logging.config.file}}. Set this to the location of a
logging.properties file with the
> [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: [email protected]
For additional commands, e-mail: [email protected]
