java.util.logging for OSGi modules cannot be configured from Control Panel

• Type: Bug
• Status: Verified
• Resolution: Unresolved
• Affects Version/s: Master
• Fix Version/s: None
• Component/s: Core Infrastructure > Log Bridge
• Labels: None
• Fix Priority: 2

org.apache.juli.ClassLoaderLogManager that we use for Tomcat returns different instances of java.util.logging.Logger for different caller ClassLoaders.

Calling Log4JUtil from com.liferay.server.admin.web.internal.portlet.action.EditServerMVCActionCommand returns Logger instance using server-admin-web TCCL.

The object instance is different from the Logger instance that OSGi modules obtained using their bundle ClassLoader.

This ends up on setting the log level on a wrong Logger instance.