Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

12.4. Per-deployment Logging

12.4.1. About Per-deployment Logging

Per-deployment logging allows a developer to configure in advance the logging configuration for their application. When the application is deployed, logging begins according to the defined configuration. The log files created through this configuration contain information only about the behavior of the application.
This approach has advantages and disadvantages over using system-wide logging. An advantage is that the administrator of the JBoss EAP instance does not need to configure logging. A disadvantage is that the per-deployment logging configuration is read only on startup and so cannot be changed at runtime.
Report a bug

12.4.2. Disable Per-deployment Logging

Procedure 12.8. Disable Per-deployment Logging

  • Two methods of disabling per-deployment logging are available. One works on all versions of JBoss EAP 6, while the other works only on JBoss EAP 6.3 and higher.

    • JBoss EAP 6 (all versions)

      Add the system property: 
      org.jboss.as.logging.per-deployment=false

    • JBoss EAP 6.3 (and higher)

      Exclude the logging subsystem using a jboss-deployment-structure.xml file. For details on how to do this, see Exclude a Subsystem from a Deployment in the Development Guide.
Report a bug
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat, Inc.