• Dave Syer's avatar
    Ensure embedded containers actually stop if there is an error on startup · 81a45485
    Dave Syer authored
    Both embedded containers need to be checked after starting to ensure that they
    are actually running. With Jetty it's just a question of catching an exception
    but with Tomcat it's harder (the current solution involves duplicating some
    code from initialize() into start() essentially checking the lifecycle state).
    
    Also adjusted the log levels to prevent noise at WARN level by default when
    this happens (since the exception is logged and rethrown anyway).
    
    There is still the issue of whether to fail the build in Maven or Gradle
    (separate issue really).
    
    Fixes gh-1232
    81a45485
Name
Last commit
Last update
docs Loading commit data...
eclipse Loading commit data...
spring-boot Loading commit data...
spring-boot-actuator Loading commit data...
spring-boot-autoconfigure Loading commit data...
spring-boot-cli Loading commit data...
spring-boot-dependencies Loading commit data...
spring-boot-docs Loading commit data...
spring-boot-full-build Loading commit data...
spring-boot-integration-tests Loading commit data...
spring-boot-parent Loading commit data...
spring-boot-samples Loading commit data...
spring-boot-starters Loading commit data...
spring-boot-tools Loading commit data...
spring-boot-versions Loading commit data...
.gitignore Loading commit data...
.settings-template.xml Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTING.adoc Loading commit data...
README.adoc Loading commit data...
pom.xml Loading commit data...