Uploaded image for project: 'JBoss BRMS Platform'
  1. JBoss BRMS Platform
  2. RHBRMS-134

Business-central: clean up logging configuration and libraries

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 6.1.0
    • 6.1.0
    • Business Central
    • None

      Description of problem:

      business-central.war uses slf4j, but it bundles also several logging backend jars:

      WEB-INF/lib/log4j-1.2.17.jar
      WEB-INF/lib/logback-classic-1.0.9.jar
      WEB-INF/lib/logback-core-1.0.9.jar

      There are also two configuration files, one of them configures a FileAppender logging into '/tmp/jbpm-form-modeler-app.log':

      WEB-INF/log4j.xml
      WEB-INF/classes/logback.xml

      Most containers cope well with this situation, but EWS sometimes picks up wrong logging backend and might stop logging.

      I think that there should be only slf4j-api jar bundled within business-central and logging configuration could be left on the container (not 100 % sure about this one). What do you think?

      Version-Release number of selected component (if applicable):
      BRMS 6.1.0 ER4

        1. Additional logging libraries in deployable distributions compared to EAP 6.x distribution.diff
          7 kB

              psiroky_jira Petr Široký (Inactive)
              mwinkler@redhat.com Marek Winkler (Inactive)
              Archiver:
              rhn-support-ceverson Clark Everson
              Jiří Locker Jiří Locker (Inactive)
              Jiří Locker Jiří Locker (Inactive)
              Kris Verlaenen, Maciej Swiderski (Inactive), Petr Široký (Inactive)

                Created:
                Updated:
                Resolved:
                Archived: