In WildFly (including version 37), the server logging configuration is controlled via the logging subsystem defined in the standalone.xml (or equivalent domain configuration). By default, WildFly includes handlers (e.g. console and file handlers). To reduce log noise, avoid excessive disk usage, and maintain performance, we recommend using a moderate logging level such as INFO for production systems, with DEBUG only during troubleshooting (and returning back to INFO afterward).
Steps to Edit Logging Level
3. Locate the logging subsystem definition. It will look something like:
<subsystem xmlns="urn:jboss:domain:logging: <version>">
<!-- handlers, loggers, root logger, etc. -->
</subsystem>
5. Verify the level name for the console-handler (within that subsystem) is INFO. Change it if necessary. For example:
<console-handler name="CONSOLE" autoflush="true">
<level name="INFO"/>
<formatter>
<named-formatter name="COLOR-PATTERN"/>
</formatter>
</console-handler>
6. Also check the root logger or other loggers that reference handlers:
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
Note
If you need to troubleshoot an issue you can set the level to DEBUG. Remember to return it to INFO when you are done.
Troubleshooting Logging
If you are having trouble with this logging approach, try this alternative:
In
YOUR_JBOSS_HOME_DIR\standalone\deployments\i2b2.war\WEB-INF\classes\log4j.propertiesadd
log4j.logger.edu.harvard.i2b2=DEBUG
