Solution is thus to to include slf4j-jdk14 in the system classloader: it is an implementation for slf4j that redirects all slf4j logs to JUL and that provides a basic but mature MDC implementation.
Note that we only need the MDC implementation for this issue, but since there is potentially dependencies in the kernel and in the components that relies on slf4j, slf4j-jdk14 will be already present in the system classloader and this will remove the need to include it in each components or the kernel (see PETALSDISTRIB-256 for more about that).
Solution is thus to to include slf4j-jdk14 in the system classloader: it is an implementation for slf4j that redirects all slf4j logs to JUL and that provides a basic but mature MDC implementation.
Note that we only need the MDC implementation for this issue, but since there is potentially dependencies in the kernel and in the components that relies on slf4j, slf4j-jdk14 will be already present in the system classloader and this will remove the need to include it in each components or the kernel (see
PETALSDISTRIB-256for more about that).PETALSDISTRIB-256for more about that).