How to separate Log4J application logging from the server.log in JBoss EAP 6?

Solution Verified - Updated -

Issue

  • Application logging going to server.log when log4j.xml is packaged in our application.
  • Messages are not logged in server.log. We use slf4j as our application's logging framework, but when we deploy our WAR into JBoss and invoke a component that does logging, we don't see any messages.
  • I would like to separate my application's logging configuration in a log4j.xml file outside the JBoss configuration (e.g. domain.xml or standalone.xml).
  • My logging isn't working correctly, and I'm seeing messages like:
16:17:03,188 INFO  [stdout] (Finalizer) log4j: Finalizing appender named [myAppender1].
16:17:03,189 INFO  [stdout] (Finalizer) log4j: Finalizing appender named [myAppender2].
  • logging-profile not working in domain mode

    • Is it possible to create the separate log file for each application where app1.war and app2.war contains same package name ?
    app1.war --> app1.log
    app2.war --> app2.log 
    
  • No logging from EJBs and Servlets packaged in the EAR . We've tried putting the following jboss-deployment-structure.xml within the EJB's META-INF folder with no success:
  • Exclude JBoss Logging Subsystem for Deployments.
  • How to configure logging for our applications to use the logging APIs shipped with our deployment ?.

Environment

  • Red Hat 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
Close

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