23.1 Startup failure
If your application fails to start, registered FailureAnalyzers
get a chance to provide a dedicated error message and a concrete action to fix the problem. For instance if you start a web application on port 8080
and that port is already in use, you should see something similar to the following:
*************************** APPLICATION FAILED TO START *************************** Description: Embedded servlet container failed to start. Port 8080 was already in use. Action: Identify and stop the process that's listening on port 8080 or configure this application to listen on another port.
Note | |
---|---|
Spring Boot provides numerous FailureAnalyzer implementations and you can add your own very easily. |
If no failure analyzers are able to handle the exception, you can still display the full auto-configuration report to better understand what went wrong. To do so you need to enable the debug
property or enable DEBUG
logging for org.springframework.boot.autoconfigure.logging.AutoConfigurationReportLoggingInitializer
.
For instance, if you are running your application using java -jar
you can enable the debug
property as follows:
$ java -jar myproject-0.0.1-SNAPSHOT.jar --debug