Fix: set the logger level to prevent unexpected level inheritance

[lttng-tools.git] / tests / regression / ust / java-log4j / JTestLTTng.java

diff --git a/tests/regression/ust/java-log4j/JTestLTTng.java b/tests/regression/ust/java-log4j/JTestLTTng.java
index 0019cb825b7d4fff1a4163d5a1fb3e102540df2d..48cb13459008267d42850a4ed6391f314ebc8e60 100644 (file)
--- a/tests/regression/ust/java-log4j/JTestLTTng.java
+++ b/tests/regression/ust/java-log4j/JTestLTTng.java
@@ -21,7 +21,7 @@ import java.lang.Integer;
 
 import org.apache.log4j.Logger;
 import org.apache.log4j.BasicConfigurator;
-
+import org.apache.log4j.Level;
 import org.lttng.ust.agent.LTTngAgent;
 
 public class JTestLTTng
@@ -37,6 +37,18 @@ public class JTestLTTng
                int fire_debug_tp = 0;
                int fire_second_tp = 0;
 
+               /*
+                * Set lowest level to make sure all event levels are logged.
+                * Any jar can override the default log4j rootLogger level
+                * and a logger with no explicit level defaults to the non-null
+                * parent level. Events could be ignored if the inherited value
+                * is too low, thereby failing the test.
+                *
+                * See BSF  -> https://issues.apache.org/jira/browse/BSF-24
+                */
+               lttng.setLevel(Level.ALL);
+               lttng2.setLevel(Level.ALL);
+
                if (args.length > 2) {
                        fire_debug_tp = Integer.parseInt(args[2]);
                }