Uploaded image for project: 'SLF4J'
  1. SLF4J
  2. SLF4J-324

Initializing org.slf4j.helpers.Util fails if SecurityManager denies "createSecurityManager"

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.7.12
    • Fix Version/s: 1.7.13
    • Component/s: Core API
    • Labels:
      None
    • Environment:

      WebSphere 8.0

      Description

      When using SLF4J in a WebSphere Application Server with a security policy that forbids "createSecurityManager", startup of SLF4J fails with a java.security.AccessControlException. Since you can't override the Constructor of SecurityManager and disable this check (which would defeat the purpose of the SecurityManager), I think the best way to handle this is Lazy Initialisation of SECURITY_MANAGER in org.slf4j.helpers.Util.

      I don't know how performance-critical this is, but since it's currently only used for a debugging feature that can be disabled in a production environment, I see no harm.

        Attachments

          Activity

            People

            • Assignee:
              ceki Ceki Gülcü
              Reporter:
              tgr Tobias Gruetzmacher
            • Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: