The JBoss Enterprise Application Platform allows us to deploy and manage Java-based applications quickly and easily — or, rather, it should. There are times, however, when JBoss fails to deploy, even when everything _looks_ like it should work from the outside. In these times, we want to leverage JBoss’s logging systems to troubleshoot our deployment and fix any outstanding issues.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Reproduce the Issue.
- Start JBoss EAP and make sure it starts successfully.
- Access the JBoss CLI.
- Attempt to deploy the application.
- Review the Logs to Diagnose the Issue.
- Review the last few logs input in the
server.logerror. Note that while the JBoss EAP service started, there were errors. - To discover what the errors during startup were, we can use the
read-boot-errorscommand.
- Review the last few logs input in the
- Resolve the Issue.
- Log out of the JBoss CLI.
- Use the
lsofcommand to view which processes are on port 8080. - Kill the process.
- Restart JBoss EAP.
- Confirm the Application Deploys Successfully.
- Return to the JBoss CLI.
- Ensure there were no boot errors.
- Deploy the application.
