In Wildfly 10 the server logging configuration is defined in the standalone.xml file. By default JBoss has included two handlers; One for logging to the console and another for logging to a file. In order to maximize the speed of your server and to prevent running out of space our recommendation is to have the level of logging set to a low level such as INFO.
Steps to Edit Logging Level
| indent |
|---|
|
1. Go to the following directory: |
| indent |
|---|
|
YOUR_JBOSS_HOME_DIR\standalone\configuration\standalone.xml |
| indent |
|---|
|
2. Open the standalone.xml file to edit its contents. |
| indent |
|---|
|
3. The handlers are in the urn:jboss:domain:logging: subsystem |
| indent |
|---|
|
5. Verify the level name for the console-handler is INFO. Change it if necessary. |
| indent |
|---|
|
| Code Block |
|---|
| <subsystem xmlns="urn:jboss:domain:logging:7.0">
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<named-formatter name="COLOR-PATTERN"/>
</formatter>
</console-handler>
|
|
| indent |
|---|
|
6. Save the changes and close the file. |
| Info |
|---|
|
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
| indent |
|---|
|
YOUR_JBOSS_HOME_DIR\standalone\deployments\i2b2.war\WEB-INF\classes\log4j.properties |
add
| Code Block |
|---|
log4j.logger.edu.harvard.i2b2=DEBUG |
