Fix: set the logger level to prevent unexpected level inheritance
authorJonathan Rajotte <jonathan.rajotte-julien@efficios.com>
Sat, 28 May 2016 06:34:23 +0000 (02:34 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Sat, 28 May 2016 06:43:09 +0000 (02:43 -0400)
commit70cfe01dca817811451fe3748ace217aa81bbf9f
treecaed6f788e2dae624de68c15fc7b3c5eb0a00993
parent1322430d56430c0ee1fb9bf55882f215a89d51ec
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.025292 seconds and 4 git commands to generate.