Developers Getting Started With i2b2
Space shortcuts
Space Tools

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin


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
Level1

1. Go to the following directory:


indent
Level3

YOUR_JBOSS_HOME_DIR\standalone\configuration\standalone.xml


indent
Level1

2. Open the standalone.xml file to edit its contents.


indent
Level1

3. Locate the <profile> section of the xml document.


indent
Level1

4. The handlers are in the urn:jboss:domain:logging:1.1 subsystem


indent
Level1

5. Verify the level name for the console-handler is INFO. Change it if necessary.


indent
Level2


Code Block
xml
xml
<periodic-rotating-file-handler name="FILE">
	<formatter>
		<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
	</formatter>
	<file relative-to="jboss.server.log.dir" path="server.log"/>
	<suffix value=".yyyy-MM-dd"/>
	<append value="true"/>
</periodic-rotating-file-handler>



indent
Level1

6. Save the changes and close the file.


Info
titleNote

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
    Level3

    YOUR_JBOSS_HOME_DIR\standalone\deployments\i2b2.war\WEB-INF\classes\log4j.properties


    add 

    Code Block
    log4j.logger.edu.harvard.i2b2=DEBUG