Don't assume that Log4j and JUL share the same log level mappings
authorJérémie Galarneau <jeremie.galarneau@efficios.com>
Mon, 31 Aug 2015 22:32:16 +0000 (18:32 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Tue, 8 Sep 2015 13:07:17 +0000 (09:07 -0400)
commit152463d94c5d1eea6394095c9a55ec5020f7dc71
tree7efc5364fa3dfe249ec4b60807459e001be4d8f4
parentab24e5255a73329d5117669289ee95061dd498b5
Don't assume that Log4j and JUL share the same log level mappings

We explicitly set the log level of Log4j events to
LTTNG_LOGLEVEL_LOG4J_ALL instead of relying on the fact that
LTTNG_LOGLEVEL_LOG4J_ALL and LTTNG_LOGLEVEL_JUL_ALL are mapped to the
same value.

The resulting additional branch does not seem to incur a significant
performance penalty and, as such, is deemed acceptable.

Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
src/bin/lttng/commands/enable_events.c
This page took 0.026002 seconds and 4 git commands to generate.