Fix: set the logger level to prevent unexpected level inheritance
authorJonathan Rajotte <jonathan.rajotte-julien@efficios.com>
Thu, 26 May 2016 22:14:37 +0000 (18:14 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Sat, 28 May 2016 06:35:55 +0000 (02:35 -0400)
commitf59a892fafb8de6f076376268224cb6a34afca04
tree5282c093d329a10d09f26bf165333b804640933c
parent5de63f6d18f9b58a65b50c8e773cc44a2bc37e0a
Fix: set the logger level to prevent unexpected level inheritance

BSF and other jars can ship with an embedded log4j.properties
file. This causes problem when launching an application with a general
class path (e.g /usr/share/java/*) since log4j will look for a
configuration file in all loaded jars. If any contains a directive for
the root logger, it will affect any logger with no level that are
directly under the root logger. This can result in an unexpected
behaviour (e.g no events triggered etc.).

Link: https://issues.apache.org/jira/browse/BSF-24
Signed-off-by: Jonathan Rajotte <jonathan.rajotte-julien@efficios.com>
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
tests/regression/ust/java-log4j/JTestLTTng.java
This page took 0.025607 seconds and 4 git commands to generate.