Isolating log4j configuration to a scoped application

Solution Unverified - Updated -

Issue

  • If we want to run multiple instances of an application on the same server, and would like to have a separate log file for each application. Since they are the same application, the log4j configuration can't easily split the output up to different files without implementing filters. An alternative is to take advantage of classloader scoping and let each individual application have their own log4j instance. This allows all logging specific to the JBoss Server to continue to go to the default server.log as usual while each application has their own separate log.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 5.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.