In case of classpath problems, JHades allows to gather from the runtime environment information that is important to understand what is going on. The information that JHades reports is not readilly available in stack traces, logs, etc.

Documentation for using JHades is available, it’s also possible to upload a WAR and view an online report. A standalone jar exists for offline inspection of WAR files. JHades can be included in a web application startup via a servlet listener in order to debug server startup problems.

Comment here for questions/suggestions/thoughts on how to tackle these problems: