Separating 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.
  • I would like to separate application logging configuration file outside the JBoss configuration
  • 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 do we configure logging to use our logging APIs.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6
  • Log4j / slf4j / custom logging API deployed with application.
  • log4j.xml or logj.propertiesconfiguration
  • Per application loggging files

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