-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding circuitBreaker filter in mvc throws IllegalArgumentException #3327
Comments
I have the same issue. The yaml based configuration doesn't seem to register the circuitbreaker @Bean
public RouterFunction<ServerResponse> routeConfig() {
return route("customer_route")
.route(path("/customer/**").or(path("/customer")), http("http://localhost:8080"))
.filter(circuitBreaker(config -> config.setId("customerCircuitBreaker")
.setStatusCodes("500")))
.build();
} |
May I handle this issue? I have an idea to work on this. |
findOperation method will not show any useful information when binding yaml properties to each class instances. Such Logging will provide a mean to evaluate failure in binding yaml properties. spring-cloud#3327
…elds to resolve) (RouterFunctionHolderFactory) Given yaml Properties, CircuitBreaker(`CircuitConfig`) method passes binding test even when given value is `ID` not `CircuitConfig` - operation method that is annotated with @configuration always pass binding test [findOperation] thereby creating wrong binding from property to method Introducing Priority will resolve methods without @configuration to be processed first and @configuration will be matched the last. spring-cloud#3327
…g yaml properties to each class instances. Such Logging will provide a mean to evaluate failure in binding yaml properties. spring-cloud#3327
Given yaml Properties, CircuitBreaker(`CircuitConfig`) method passes binding test even when given value is `ID` not `CircuitConfig` - operation method that is annotated with @configuration always pass binding test [findOperation] thereby creating wrong binding from property to method Introducing Sorting to the operations, it will resolve methods without @configuration to be processed first and @configuration will be matched the last. spring-cloud#3327
Given Situation: yaml file fails to bind to the CircuitBreaker HandlerFilterFunction
|
i using
java 21
spring boot 3.2.4
spring cloud dependencies 2023.0.1
Adding circuitBreaker filter in mvc throws IllegalArgumentException
An error occurs when the circuitBreaker filter is set as below and passes through the registered route.
spring-cloud-starter-circuitbreaker-reactor-resilience4j dependency is added
Did I miss anything?
The text was updated successfully, but these errors were encountered: