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, 1 Sep 2015 16:03:08 +0000 (12:03 -0400)
commit34aa3685e3196d6044cc700734f799a112d74a9c
tree27a3a3a191414630a68b6ff6e516c540510d9e01
parent9232818fac36af5165979d38b2f9a67a56ad8819
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.033018 seconds and 4 git commands to generate.