How does JBoss EAP 6 manage System.out?

Solution Verified - Updated -

Issue

  • While using System.out.println() in EAP 6, this call gets sent through JBoss LogManager and ultimately gets written by the JBoss ConsoleHandler. Why users can not log straight to System.out?
  • While installing our own ConsoleAppender for 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 STDERR and STDOUT logs 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 of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.