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

Logging Profile outputs messages to the wrong Handler

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 6.4.0.GA
    • Logging
    • Hide

      Prerequisites: you need a running A-MQ 6 server on default ports

      How to reproduce the issue:
      1) Configure JBoss EAP 6.4 with fuse-eap-installer-6.3.0.redhat-187 and the standalone-full.xml configuration contained in the reproducer.zip

      2) Build both applications with:
      $ mvn clean install

      3) Copy eap-jms-6.3.war and eap-jms2-6.3.war into the deployments folder of EAP

      Now the Camel context "eap-jms" will write messages with "APP-1" to $JBOSS_HOME/standalone/log/gepard_order_event1.log
      The Camel context "eap-jms2" will write messages with "APP-2" to $JBOSS_HOME/standalone/log/gepard_order_event2.log

      After a while (a Timer trigger publishing of new messages), observe the issue:

      $ [francesco@localhost log]$ grep "APP-2" gepard_order_event1.log | wc -l
      18

      Messages of the Application2 are found in the first log file gepard_order_event1.log !!

      Show
      Prerequisites: you need a running A-MQ 6 server on default ports How to reproduce the issue: 1) Configure JBoss EAP 6.4 with fuse-eap-installer-6.3.0.redhat-187 and the standalone-full.xml configuration contained in the reproducer.zip 2) Build both applications with: $ mvn clean install 3) Copy eap-jms-6.3.war and eap-jms2-6.3.war into the deployments folder of EAP Now the Camel context "eap-jms" will write messages with "APP-1" to $JBOSS_HOME/standalone/log/gepard_order_event1.log The Camel context "eap-jms2" will write messages with "APP-2" to $JBOSS_HOME/standalone/log/gepard_order_event2.log After a while (a Timer trigger publishing of new messages), observe the issue: $ [francesco@localhost log] $ grep "APP-2" gepard_order_event1.log | wc -l 18 Messages of the Application2 are found in the first log file gepard_order_event1.log !!

    Description

      Context: Several war files using Camel Routes, each one configured to use a different Logging Profile.
      Requirement: We need that each web application logs to a different file, as configured in its Logging profile.
      Issue: We found out that sometimes the logs of one application go to the wrong file.
      We also notice that this info is mostly related to the application startup, the camel route initialization, and the jms broker connection.

      Attachments

        1. Gepard-esb-logging-1.0-SNAPSHOT.patched.war
          11.31 MB
        2. loggingTestReproducer.rar
          63 kB
        3. reproducer.tar.gz
          19 kB
        4. reproducer.zip
          8.09 MB

        Issue Links

          clones

          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

          Activity

            People

              jperkins-rhn James Perkins
              fmarchio@redhat.com Francesco Marchioni (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: