davsclaus opened a new issue, #81: URL: https://github.com/apache/camel-jbang-examples/issues/81
The `fail-well/circuit-breaker` example (#80) logs `CamelCircuitBreakerState` on every line because, in Camel 4.22, the fallback cannot tell a call that failed from a call the open breaker never attempted: `CamelCircuitBreakerResponseShortCircuited` is `true` for every fallback and `CamelCircuitBreakerResponseRejected` is only set when there is no fallback. Camel 4.23 changes that: - [CAMEL-24818](https://issues.apache.org/jira/browse/CAMEL-24818) (apache/camel#26602): `CamelCircuitBreakerResponseRejected` is set inside the `onFallback`, `true` when the breaker was open or the bulkhead full, `false` when the call was made and failed. - [CAMEL-24819](https://issues.apache.org/jira/browse/CAMEL-24819): fallback, timed out and bulkhead rejected calls are counted in JMX, the dev console, `camel get circuit-breaker` and the TUI. When the example runs on 4.23, update it: - In `onFallback`, choose the body on `${exchangeProperty.CamelCircuitBreakerResponseRejected}`: "breaker open, supplier not called, using last known stock" versus "supplier failed, using last known stock", so the log shows the difference the breaker makes. - Keep the state on the line; the README's "How it works" then explains both. - Mention `camel get circuit-breaker` in "Try changing" to watch the fallback and reject counters while it runs. - Update the Citrus test's expected lines. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
