Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3307

stdout lost with log4j.xml per-deployment logging

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 8.1.0.CR1
    • Logging
    • None

      With log4j.xml per-deployment logging, the appenders are added within the org.apache.log4j.Logger.getLogger() call. Currently System.out.println("foo") initializes no-handler "stdout" logger which is essencially no-op.

      To workaround, initializing the following 2 loggers before using System.out/err.

      org.apache.log4j.Logger.getLogger("stdout");
      org.apache.log4j.Logger.getLogger("stderr");
      

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

                Created:
                Updated:
                Resolved: