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

Logging handler lost due to conflict handlers in logging.properties and standalone.xml

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 3.0.0.Beta11
    • 2.0.10.Final
    • Logging
    • None

      Console logging doesn't work after logging subsystem init with the following configuration.

      • logging.properties is configured with ASYNC with CONSOLE handlers.
      • standalone.xml is configured with stock FILE and CONSOLE handlers.

      Background of why there is a mismatch between logging.properties and standalone.xml, EAP image for OpenShift is configured with ASYNC with CONSOLE handlers by default. But users can customize standalone.xml and apply custom configuration based on the stock standalone.xml.

      Expected result is logging configuration from standalone.xml is applied once logging subsystem come up regardless the mismatch.

      Most likely related to WFCORE-159.

        1. logging.properties
          2 kB

              jperkins-rhn James Perkins
              rhn-support-tkimura Takayoshi Kimura
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: