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

[GSS](7.1.0) logging profile with apache commons does not work

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.DR6
    • 7.1.0.DR5
    • Logging
    • None
    • Documentation (Ref Guide, User Guide, etc.), Release Notes
    • Fix is merged upstream.
    • Workaround Exists
    • Hide

      use jboss-logging

      Show
      use jboss-logging
    • Hide

      1 - Create an application that uses apache commons to log, for example:

      import org.apache.commons.logging.Log;
      import org.apache.commons.logging.LogFactory;

      public class AppConfig

      { private static final Log logger = LogFactory.getLog(AppConfig.class); .... logger.info(...) }

      2 - create two logging profiles:

      • app1.war
        Logging-Profile: app1-logging
      • app2.war
        Logging-Profile: app2-logging

      Actual results:

      • app1.war writes a log messages with category a.b.c, the ROOT-logger from the logging-profile app1-logging handles the message
      • after that app2.war writes a log message with the same category a.b.c, this message is also handled by the ROOT-logger from the logging-profile app1-logging and not, as expected, by the ROOT-logger from logging-profile app2-logging

      Expected results:

      app1.war writes logs to app1-logging logging profile log file
      app2.war writes logs to app2-logging logging profile log file

      Show
      1 - Create an application that uses apache commons to log, for example: import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; public class AppConfig { private static final Log logger = LogFactory.getLog(AppConfig.class); .... logger.info(...) } 2 - create two logging profiles: app1.war Logging-Profile: app1-logging app2.war Logging-Profile: app2-logging Actual results: app1.war writes a log messages with category a.b.c, the ROOT-logger from the logging-profile app1-logging handles the message after that app2.war writes a log message with the same category a.b.c, this message is also handled by the ROOT-logger from the logging-profile app1-logging and not, as expected, by the ROOT-logger from logging-profile app2-logging Expected results: app1.war writes logs to app1-logging logging profile log file app2.war writes logs to app2-logging logging profile log file

    Description

      All entry logs go to the log file of the first accessed application logging profile.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-14458 [GSS](7.1.z) org.apache.commons.discovery.DiscoveryException: Unable to instantiate implementation class for org.apache.commons.logging.LogFactory

          • 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.
          • Closed
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-254 logging-profiles doesn't work with Apache Common Logging

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFLY-7077 logging profile with apache commons does not work

          • 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.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5933 [GSS](7.0.z) logging profile with apache commons does not work in JBoss EAP 7

          • 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

          Bug - A problem that impairs or prevents the functions of the product. WFLY-7077 logging profile with apache commons does not work

          • 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.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-5897 (7.1.0) Upgrade to WildFly Core 3.0.0.Alpha8

          • 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 related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12041 Please remove eap7-jcl-over-slf4j package from EAP7.1 erratas

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              jperkins-rhn James Perkins
              rhn-support-lkonno Leticia Konno
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: