Java EE 7 SDK

Troubleshooting Sample Applications

There are three components which contribute to the smooth working of sample applications. These components are the build infrastructure, the application server, and the sample application. Follow the common build instructions to set up the build infrastructure and the application server. To troubleshoot a sample application, follow this procedure:

Use the fine-grained Maven goals to isolate the problem. For example, if mvn cargo:run causes an exception then try to run the constituent Maven targets like compile, install, verify, and cargo:run separately.
Refer to the exception in detail and try to fix it.
Refer to the server.log file of the application server for clues or messages.
Try alternative ways of doing the same thing. For example, if deployment fails, try deploying through the Admin Console or CLI.
Before retrying, run the clean goal to remove the generated directories.
Restart the application server. This might be needed to apply certain non-dynamic configuration changes.
Make sure the user ID and password or the credentials are valid.
If the application uses JDBC resources, make sure that the database server is up and running and the resources are set up properly. Likewise, if the application uses JMS resources, make sure the MQ server is running and the JMS resources are configured properly.
The recommended version of Maven is 3.0.5.

The above list is evolving and is by no means exhaustive.