spring-cloud-circuitbreaker: Resilience4j's TimeLimiter triggered after feign response in postConstruct() callback

Describe the bug Like the title said. I found that Resilience4j’s TimeLimiter always triggered even feign client received response when feign method’s return type is not void.

I’m using: OpenJDK 1.8.0_292-b10 and 11.0.11.9-hotspot Spring boot 2.5.2 Spring cloud 2020.0.3

Sample Here: https://github.com/DevDengChao/resilience4j-time-limiter-triggered-after-feign-response

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 18 (6 by maintainers)

Most upvoted comments

If it is a functional requirement of your application then you could try other startup mechanisms, e.g.

https://www.baeldung.com/running-setup-logic-on-startup-in-spring