为什么Springboot 初始化模板 启动自动关闭没有报错信息

Question

  .   ____          _            __ _ _ /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/  ___)| |_)| | | | | || (_| |  ) ) ) )  '  |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot ::        (v1.4.5.RELEASE)2017-04-13 09:30:24.619  INFO 5132 --- [           main] com.example.DemoApplication              : Starting DemoApplication on teacher023 with PID 5132 (C:\Users\Administrator\IdeaProjects\myth\demo\target\classes started by Administrator in C:\Users\Administrator\IdeaProjects\myth)2017-04-13 09:30:24.619  INFO 5132 --- [           main] com.example.DemoApplication              : No active profile set, falling back to default profiles: default2017-04-13 09:30:24.681  INFO 5132 --- [           main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@3b69e7d1: startup date [Thu Apr 13 09:30:24 GMT+08:00 2017]; root of context hierarchy2017-04-13 09:30:25.742  INFO 5132 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Registering beans for JMX exposure on startup2017-04-13 09:30:25.758  INFO 5132 --- [           main] com.example.DemoApplication              : Started DemoApplication in 1.607 seconds (JVM running for 1.979)2017-04-13 09:30:25.758  INFO 5132 --- [       Thread-1] s.c.a.AnnotationConfigApplicationContext : Closing org.springframework.context.annotation.AnnotationConfigApplicationContext@3b69e7d1: startup date [Thu Apr 13 09:30:24 GMT+08:00 2017]; root of context hierarchy2017-04-13 09:30:25.758  INFO 5132 --- [       Thread-1] o.s.j.e.a.AnnotationMBeanExporter        : Unregistering JMX-exposed beans on shutdownProcess finished with exit code 0

Answer 1

没有引入spring-boot-starter-web包，此时的程序没有运行在服务器上，跟普通的java程序一样。

Answer 2

 <dependency>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-tomcat</artifactId>
        <scope>provided</scope>
    </dependency>
    <scope>provided</scope>删除就好了

Answer 3

可能有些启动时静态实现的功能初始化出错，导致启动失败，自动关闭。