Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-26026

[GSS](8.0.z) WFCORE-6589 - MDC is ignored when using Log4J 2 API

    XMLWordPrintable

Details

    • False
    • None
    • False
    • +
    • Known Issue
    • Hide
      1. Add below pattern-formatter in logging susbsystem of handler :
      2. <formatter>
        <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) [deployment=%X\{deployment}] %s%E%n"/>
        </formatter>
      3. Deploy [^logging-poc-0.0.1-SNAPSHOT.war]and check the results.
      Show
      Add below pattern-formatter in logging susbsystem of handler : <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) [deployment=%X\{deployment}] %s%E%n"/> </formatter> Deploy [^logging-poc-0.0.1-SNAPSHOT.war] and check the results.

    Description

      When logging via the Log4J 2 API MDC-variables are not filled in the output. The output of the reproducer is as follows :

      15:31:38,326 INFO [TestServlet] (default task-3) [deployment=] Log4J 2
      15:31:38,327 INFO [TestServlet] (default task-3) [deployment=logging-poc] Log4J 1
      15:31:38,328 INFO [TestServlet] (default task-3) [deployment=logging-poc] SLF4J 1
      15:31:38,328 INFO [TestServlet] (default task-3) [deployment=logging-poc] java.util.logging
      15:31:38,328 INFO [TestServlet] (default task-3) [deployment=logging-poc] commons-logging

      Expactation: MDC-Variables are considered regardless of logging API.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-25900 [GSS](7.4.z) MDC is ignored when using Log4J 2 API

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-6589 MDC is ignored when using Log4J 2 API

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-26024 (8.0.z) Upgrade log4j2-jboss-logmanager from 1.1.1.Final to 1.1.2.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              rhn-support-rbudinsk Rastislav Budinský
              rhn-support-rbudinsk Rastislav Budinský
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: