Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.2.0.Final, 3.3.0.Beta1
    • Fix Version/s: 3.2.1.Final, 3.3.0.Beta1
    • Component/s: None
    • Labels:
      None

      Description

      There seems to be a typo in org.jboss.logging.LoggingProviders in the method tryLog4j(): the logging provider implementation used is Log4j2LoggerProvider, whereas it should be Log4jLoggerProvider.

      The net effect is that if I have log4j jars on the classpath and include a log4j configuration, the configuration gets parsed but log4j is not used as the logging provider; instead, JDK logging provider is used.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jamezp James Perkins
                Reporter:
                rachmato Richard Achmatowicz
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: