[jboss-jira] [JBoss JIRA] (WFLY-3307) stdout lost with log4j.xml per-deployment logging

Takayoshi Kimura (JIRA) issues at jboss.org
Thu May 1 05:01:56 EDT 2014


Takayoshi Kimura created WFLY-3307:
--------------------------------------

             Summary: stdout lost with log4j.xml per-deployment logging
                 Key: WFLY-3307
                 URL: https://issues.jboss.org/browse/WFLY-3307
             Project: WildFly
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Logging
    Affects Versions: 8.1.0.CR1
            Reporter: Takayoshi Kimura
            Assignee: James Perkins


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.

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



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


More information about the jboss-jira mailing list