How does JBoss EAP 6 manage System.out?
Issue
- While using
System.out.println()in EAP 6, this call gets sent through JBoss LogManager and ultimately gets written by the JBossConsoleHandler. Why users can not log straight toSystem.out? - While installing our own
ConsoleAppenderfor the application, getting the output like this:
11:35:36,582 INFO [stdout] (http-/127.0.0.1:8080-1) DEBUG [http-/127.0.0.1:8080-1] [com.redhat.gss.log.LogbackTest] - ***DEBUG: Kyle
11:35:36,583 INFO [stdout] (http-/127.0.0.1:8080-1) INFO [http-/127.0.0.1:8080-1] [com.redhat.gss.log.LogbackTest] - ***INFO: Kyle
Notice all the above logs are at INFO level regardless of what is configured, and every message is prefixed with [stdout]. Why does JBoss interrupt with our ConsoleAppender?
- How can I separate
STDERRandSTDOUTlogs from server.log in JBoss EAP 6?
Environment
- JBoss Enterprise Application Platform (EAP)
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.