Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-82456

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

    Details

    • Fix Priority:
      2

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              support-lep@liferay.com SE Support
              Reporter:
              tomas.polesovsky Tomáš Polešovský
              Participants of an Issue:
              Recent user:
              Koor Gai
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Days since last comment:
                3 years, 49 weeks, 6 days ago

                  Packages

                  Version Package