Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3336

Not able to separate application(EAR) logging with the use of logging profile

    XMLWordPrintable

Details

    • Hide

      1. Start server instance with attached standalone.xml file(Logging subsystem contains logger-profile configuration)
      2. Deploy both EAR files and access them
      3. Check log files.

      Note: The following reproducer only works on WildFly Full, but the issue itself is likely in WIldFly Core.
      To reproduce with the attached logging-profile.zip do the follow:

      1. Build the project and deploy the EAR.
        1. With maven you can do mvn clean isntall && cd ear && mvn wildfly:deploy -Pconfigure-logging
      2. In a browser go to http://localhost:8080/test-war-one/rest/log
      3. Next go to http://localhost:8080/test-war-two/rest/log, here you'll see less log messages
      4. Now if you go to http://localhost:8080/test-war-one/rest/read you'll see a mix of log messages from both WAR's
      Show
      1. Start server instance with attached standalone.xml file(Logging subsystem contains logger-profile configuration) 2. Deploy both EAR files and access them 3. Check log files. Note: The following reproducer only works on WildFly Full, but the issue itself is likely in WIldFly Core. To reproduce with the attached logging-profile.zip do the follow: Build the project and deploy the EAR. With maven you can do mvn clean isntall && cd ear && mvn wildfly:deploy -Pconfigure-logging In a browser go to http://localhost:8080/test-war-one/rest/log Next go to http://localhost:8080/test-war-two/rest/log , here you'll see less log messages Now if you go to http://localhost:8080/test-war-one/rest/read you'll see a mix of log messages from both WAR's

    Description

      Two ear files are deployed on EAP instance and both are configured to use different logging profile through EAR/META-INF/MANIFEST.MF file.
      WAR file from EAR uses some libraries those are present in the "lib" folder of each ear file. Application1.ear which logs in app1.log and Application2.ear which logs in app2.log.
      when we access application we can see logging from EAR1 into EAR2 log file .

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-13322 (7.2.0) Not able to separate application(EAR) logging with the use of logging profile

          • 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. JBEAP-13502 [GSS](7.1.z) Not able to separate application(EAR) logging with the use of logging profile

          • 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

          Task - Represents a small unit of work that is not end-user facing. WFLY-9431 Write a test to ensure a library in an EAR uses the correct log context

          • 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.
          • Open
          relates to

          Task - Represents a small unit of work that is not end-user facing. JBEAP-14157 [EAT] : Testcase for JBEAP-13502 so that it can be tested with all the servers.

          • 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

          Activity

            People

              jperkins-rhn James Perkins
              jperkins-rhn James Perkins
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: