[QPID-8017] [Broker-J] [BDB] JE log events written at JUL level FINE and below not included in the log produced by a BrokerLogger

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: qpid-java-6.1, qpid-java-broker-7.0.0
• Fix Version/s: qpid-java-broker-7.0.1
• Component/s: Broker-J
• Assignee: Unassigned
• Reporter: Keith Wall
• Created: 07/Nov/17 10:47
• Updated: 02/Oct/19 19:21
• Resolved: 12/Jan/18 17:48

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.

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

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.