When you are working on applications running on the JBoss Application Server you will, sooner or later, encounter problems that require analyzing logfiles. JBoss uses Logfile-Codes (Is that the correct word?) that make it easy to search for specific log messages, independent of you Locale or your ability to type the error message correctly.

For example, if you want to know if the server has started with errors you can search for the code JBAS015875. If your server runs with an English Locale the full log message could look like

ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.4.15.GA (AS 7.5.15.Final-redhat-3) started (with errors) in 3670ms — Started 200 of 300 services (10 services failed or missing dependencies, 120 services are lazy, passive or on-demand)

Since I haven’t found a list of those Logfile-Codes I have compiled one myself and want to share it here. I hope someone will find this list useful.

• JBAS015874: Server has started successfully
• JBAS015875: Server has started with errors
• JBAS015899: Server begins to start
• JBAS015986: Host Controller shutdown has been requested via an OS signal
• JBAS015950: Server has stopped
• JBAS015962: Http management interface listening
• JBAS015954: Admin console is not enabled
• JBAS012119: Cancelled task by interrupting thread Thread
• JBAS015876: Starting deployment
• JBAS010403: Deploying JDBC-compliant driver
• JBAS017100: Listening on 127.0.0.1:19999
• JBAS010400: Bound data source
• JBAS016002: Processing weld deployment
• JBAS016012: Deployment contains CDI annotations but beans.xml was not found
• JBAS018210: Register web context
• JBAS016005: Starting Services for CDI deployment
• JBAS011402: Starting Persistence Unit Service
• JBAS010281: Started cache from app-cache container
• JBAS018224: Unregister web context
• JBAS010409: Unbound data source
• JBAS011403: Stopping Persistence Unit Service
• JBAS016009: Stopping weld service for deployment
• JBAS015877: Stopped deployment