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:37:17 +0000 (02:37 -0400)
commit234a7d9785e21a3b3ee1efa5df416714079a899b
tree8481cde0338a9de8cec67137e5409558e9150cad
parenta6793259f72179199f999fd34ffb94e2f80169a8
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.025036 seconds and 4 git commands to generate.