最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

spring boot - Unable to connect to eureka after migraiton to springboot 3.4.2 - Stack Overflow

programmeradmin6浏览0评论

We are migrating our application from spring boot 3.3.4 to spring boot 3.4.2 We are using netflix eureka and api-gateway. We are deploying the application to openshift.

application.yaml we have (even with spring boot 3.3.4):

eureka:
  instance:
    prefer-ip-address: true
    hostname: api-gateway-service
  client:
    serviceUrl:
      defaultZone: ${EUREKA_URI:http://localhost:9092/eureka}

(We have set the value of EUREKA_URI as http://v42rest-eureka:9092/eureka)

After migration, the api-gateway is not able to forward the requests to the applications. We see that all the applications including the gateway is registered in eureka.

But in the gateway logs, we see this error:

"comflix.discovery.DiscoveryClient","message":"Getting all instance registry info from the eureka server" "comflix.discovery.shared.transport.decorator.RetryableEurekaHttpClient","message":"Request execution failure with status code 403; retrying on another server if available","context":"default"}

We are getting the error only while getting the registry info. There is no error while registring the gateway in eureka.

I noted that there are some changes in Netflix Eureka restclient in release 3.4.2

Is anyone else facing a similar Problem?

We are migrating our application from spring boot 3.3.4 to spring boot 3.4.2 We are using netflix eureka and api-gateway. We are deploying the application to openshift.

application.yaml we have (even with spring boot 3.3.4):

eureka:
  instance:
    prefer-ip-address: true
    hostname: api-gateway-service
  client:
    serviceUrl:
      defaultZone: ${EUREKA_URI:http://localhost:9092/eureka}

(We have set the value of EUREKA_URI as http://v42rest-eureka:9092/eureka)

After migration, the api-gateway is not able to forward the requests to the applications. We see that all the applications including the gateway is registered in eureka.

But in the gateway logs, we see this error:

"comflix.discovery.DiscoveryClient","message":"Getting all instance registry info from the eureka server" "comflix.discovery.shared.transport.decorator.RetryableEurekaHttpClient","message":"Request execution failure with status code 403; retrying on another server if available","context":"default"}

We are getting the error only while getting the registry info. There is no error while registring the gateway in eureka.

I noted that there are some changes in Netflix Eureka restclient in release 3.4.2

Is anyone else facing a similar Problem?

Share Improve this question asked Mar 18 at 8:13 manoj hyandmanoj hyand 11 bronze badge
Add a comment  | 

1 Answer 1

Reset to default 0

Possibly related to - https://github/spring-cloud/spring-cloud-netflix/pull/4394/files

Fixed in 2024.0.1, try setting RequestConfig

发布评论

评论列表(0)

  1. 暂无评论