Closed Ferioney closed 1 year ago
If we don't call the create
method when normal
is called I think that would solve the problem no?
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.
it happened . the circuitbreaker always customize itselef in the “run” method and the event consumer will be added again
@Ferioney @limng06 can you confirm if this is still a problem with the latest release Spring Cloud 2021.0.0?
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.
When you use Resilience4JCircuitBreakerFactory.addCircuitBreakerCustomizer() to customize an event, this event will be added in every call of the method.
We customize circuitBreaker each time when calling a method. But circuitBreaker is stored in circuitBreakerRegistry. so each time we add an event to this circuitBreaker.
In Resilience4j events store as map, that why it possible: EventProcessor
Unit test that shows defect: defectTwoSlowCircuitBreakerConsumerShouldBeCalledTwoTimesButCalledThreeTimes