Uploaded image for project: 'JBoss Log Manager'
  1. JBoss Log Manager
  2. LOGMGR-77

MDC custom parameter not logged in jboss 7.1.1

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 1.4.3.Final
    • core
    • None
    • Hide

      1- Use this Fromatter string in log configuration: %d

      {HH:mm:ss,SSS}

      %-5p %X

      {transactionId}

      [%c] (%t) %s%E%n

      2- Deploy an .ear, for example a simple web service, where the transactionId parameter is set on MDC on each method invocation, with: MDC.put("transactionId", transactionId);

      2bis- Try my configuration: In any class I instantiate the logger with: private static final LogManager LOGGER = LogManager.getInstance(myClass.class);

      where getInstance returns a org.apache.commons.logging.Log, instantiated with LogFactory.getLog(clazz);

      where LogFactory is org.apache.commons.logging.LogFactory.

      3- Try to log the parameter for debug purpose (with MDC.get("transactionId") and check the parameter is correctely set.

      4- Make the same configurations under jboss eap 6.1 free version and deploy your .ear under this server. Verify that the transactionId is correctely logged on every log line under jboss eap 6.1.

      5- Verify that under jboss-as-7.1.1, with the same configurations, the transactionId is not logged.

      Show
      1- Use this Fromatter string in log configuration: %d {HH:mm:ss,SSS} %-5p %X {transactionId} [%c] (%t) %s%E%n 2- Deploy an .ear, for example a simple web service, where the transactionId parameter is set on MDC on each method invocation, with: MDC.put("transactionId", transactionId); 2bis- Try my configuration: In any class I instantiate the logger with: private static final LogManager LOGGER = LogManager.getInstance(myClass.class); where getInstance returns a org.apache.commons.logging.Log, instantiated with LogFactory.getLog(clazz); where LogFactory is org.apache.commons.logging.LogFactory. 3- Try to log the parameter for debug purpose (with MDC.get("transactionId") and check the parameter is correctely set. 4- Make the same configurations under jboss eap 6.1 free version and deploy your .ear under this server. Verify that the transactionId is correctely logged on every log line under jboss eap 6.1. 5- Verify that under jboss-as-7.1.1, with the same configurations, the transactionId is not logged.

    Description

      The LogManager doesn't log MDC custom parameters.

      Attachments

        Activity

          People

            jperkins-rhn James Perkins
            sheriel Marco Pavone (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: