Spring 在 Eclipse 上输出 logo 和版本后启动应用程序突然停止

Question

When I execute Run As -> Java application my Spring Boot application class on Eclipse, I get Spring Boot logo and version in logs but it halts and stops after few seconds:

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/

Spring version: 1.5.9.RELEASE

There are no errors in console.

Tried but didn't help:

• Project -> Clean, project refresh on Eclipse
• gradle clean , build , eclipse from command line
• Deleted and imported project from git again
• Restart Eclipse

Tried solutions from related SO threads:

• Spring boot 1.5.2 - web application stops after loading logo?
• spring boot server stops after main method execution

Also:

• If I run tests from Eclipse, they pass successfully.
• Other Spring Boot apps run well on Eclipse.
• When I try to run application from command line with gradle bootRun , it runs smoothly.

Why does it happen? How to solve it?

Answer 1

Deleted logback.xml from src/main/resources and logback-test.xml from src/test/resources and it worked.

Answer 2

In my case It was fixed when added the spring boot web dependency

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-web</artifactId>
</dependency>

Answer 3

Spring Boot is still working, just there is no output in the console after logo. Server will startup if there are no other issues.

In my case Spring Boot console stopped logging after i renamed application.properties into core.properties (that file is referred in logback.xml)

<define name="internalFile" class="ch.qos.logback.core.property.ResourceExistsPropertyDefiner">
    <resource>application.properties</resource>
</define>

After updating the resource tag, console output was back.

Answer 4

in my case the reason was that I was using an alpha release of sl4j. When i replaced it with an older one I was able to start the spring boot application.

Answer 5

If the answers above are not satisfactory the issue in my case was that I was including dependency with its own slf4j setup, that got in clash with Spring Boot's one (old vs. new).

The problem was that the dependency was accidentally built as fat-jar.

Answer 6

I had this issue from upgrading the slf4j-api dependency from 1.X to 2.0.6 . We were able to resolve by adding slf4j-simple:2.0.6 dependency as well. The slf4j patch notes for version 2.0 go over this topic here . Spring hanging on the logo appears to be an additional side effect.

slf4j-api version	slf4j-simple version	Result	Explanation
2.0.x	2.0.x	OK	Same version for slf4j-api and provider
1.7.x	2.0.x	no bindings can be found warning message	2.0.x providers do not act as 1.7.x/1.6.x compatible bindings
2.0.x	1.7.x	no providers can be found warning message	slf4j-api 2.0.x will no longer search for StaticLoggerBinding