Spring Cloud调用RestEndpoint失败求助：Eureka教程换Parent版本后无日志

Let's walk through practical checks and fixes for your issue—since you only modified the spring-boot-starter-parent version and now face silent failures with no logs, here's where to start:

1. Rule Out Snapshot Version Instability #

You switched from a stable 1.5.4.RELEASE to a 1.5.13.BUILD-SNAPSHOT parent. Snapshot builds are unfinished, unstable releases that often have untested compatibility gaps with Spring Cloud components (like Eureka) that were built for stable Spring Boot versions.

• First, revert to a stable 1.5.x release (e.g., 1.5.22.RELEASE, the latest stable in the 1.5.x line) in your pom.xml:

  <parent>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-starter-parent</artifactId>
      <version>1.5.22.RELEASE</version>
      <relativePath/>
  </parent>
  

• Rebuild and restart all services to see if the issue resolves.

2. Force Debug Logging to Uncover Hidden Issues #

The lack of logs means we're missing critical details about what's failing. Enable verbose logging for Eureka and Spring Web components:

• Add these properties to your application.properties (or YAML equivalent) for both the Eureka server and student service:

  logging.level.org.springframework.cloud.netflix.eureka=DEBUG
  logging.level.org.springframework.web=DEBUG
  logging.level.com.netflix.discovery=DEBUG
  

• Restart everything and re-run your request. You'll now see registration attempts, connection errors, or mapping issues that were previously hidden.

3. Confirm Eureka Service Registration #

• Navigate to your Eureka dashboard (typically http://localhost:8761 by default) and check if spring-eureka-client-student-service appears under Instances currently registered with Eureka.
• If it's missing, verify the client's Eureka config properties are correct:

  eureka.client.service-url.defaultZone=http://localhost:8761/eureka/
  eureka.instance.prefer-ip-address=true
  

  Ensure defaultZone points to your running Eureka server.

4. Validate Port and Request Mapping #

• Double-check that your student service is actually running on port 8098. Look for the startup log line: Tomcat started on port(s): 8098 (http). Adjust your request URL if the port differs.
• Confirm your controller's request mapping matches exactly. It should look like this (no typos or path mismatches):

  @GetMapping("/getStudentDetailsForSchool/{schoolName}")
  public List<Student> fetchStudentsBySchool(@PathVariable String schoolName) {
      // Your business logic here
  }
  

内容的提问来源于stack exchange，提问作者Jeff Cook