Message-ID: <2048740504.7976.1711654136016.JavaMail.confluence@ip-172-30-4-17.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7975_296871889.1711654136012" ------=_Part_7975_296871889.1711654136012 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html 2.4.2.2 Wildfly Logging Configuration

2.4.2.2 Wildfly Logging Configuration


In Wildfly 10 the server l= ogging configuration is defined in the standalone.xml file= . By default JBoss has included two handlers; One for logging to the consol= e 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 t= he level of logging set to a low level such as INFO.


St= eps to Edit Logging Level


1. Go to the following directory:
=20
YOUR_JBOSS_HOME_DIR\standalone\configuration\standalone.xml
=20
2. Open the=20 standalone.xml file to edit its contents.
=20
3. The handlers are in the=20 urn:jboss:domain:logging: subsystem
=20
5. Verify the level name for the=20 console-handler is=20 INFO. Change it if necessary.
=20
=20
<sub=
system xmlns=3D"urn:jboss:domain:logging:7.0">
            <console-handler name=3D"CONSOLE">
                <level name=3D"INFO"/>
                <formatter>
                    <named-formatter name=3D"COLOR-PATTERN"/>
                </formatter>
            </console-handler>

=20
=20
6. Save the changes and close the file.

Note

If you need to troubleshoot an issue you can set the level to DEBUG. Rem= ember to return it to INFO when you are done.

Troubleshooting Logging

If you are having trouble with this logging= approach, try this alternative:

------=_Part_7975_296871889.1711654136012--