Enabling EJB Debug/Trace logging in JBoss EAP 8 / 7 / 6

Solution Verified - Updated

Environment

  • Red Hat Enterprise Application Platform (EAP)
    • 8
    • 7
    • 6

Issue

Enabling EJB and security Debug/Trace logging in JBoss EAP 7 / 6

Resolution

In the JBoss EAP profile (standalone*.xml / domain.xml) logging subsystem, enable these categories as such:

                <logger category="org.jboss.ejb.client">
                    <level name="DEBUG"/>
                </logger>
                <logger category="org.wildfly.transaction.client">
                    <level name="DEBUG"/>
                </logger>
                <logger category="org.jboss.as.config">
                    <level name="DEBUG"/>
                </logger>
                <logger category="org.jboss.remoting.remote">
                    <level name="TRACE"/>
                </logger>
                <logger category="org.jboss.security">
                    <level name="ALL"/>
                </logger>
                <logger category="org.jboss.as.security">
                    <level name="ALL"/>
                </logger>
                <logger category="org.keycloak">
                    <level name="TRACE"/>
                </logger>
                <logger category="org.picketbox">
                    <level name="ALL"/>
                </logger>
                <logger category="org.wildfly.security">
                    <level name="ALL"/>
                </logger>
                <logger category="org.wildfly.elytron">
                    <level name="ALL"/>
                </logger>
                <logger category="org.jboss.remoting">
                    <level name="ALL"/>
                </logger>
                <logger category="org.jboss.sasl">
                    <level name="ALL"/>
                </logger>
                <logger category="org.jboss.ejb">
                    <level name="ALL"/>
                </logger>
                <logger category="org.jboss.as.ejb3">
                    <level name="ALL"/>
                </logger>
                <logger category="org.wildfly.discovery">
                    <level name="ALL"/>
                </logger>
                <logger category="org.wildfly.naming">
                    <level name="ALL"/>
                </logger>

The table below presents what enabling tracing exposes for each subsystem:

SubsystemWhat it will show
org.jboss.remoting.remoteFor remoting ejb connections, it can show heartbeat

The levels of log are presented on the table below (and on the JBoss EAP 7 Configuration Guide):

Log LevelNumber of characters
ALLset min number of characters
FINEST300
FINER400
TRACE400
DEBUG500
FINE500
CONFIG700
INFO800
WARN900
WARNING900
ERROR1000
SEVERE1000
FATAL1000
OFFDoes not display any log message.

Related Solution
Enabling security Debug/Trace logging in JBoss EAP 6 or 7

Components
Category

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.