Hi Claus, Not quite. I am expecting a timeout and a timeout exception to be thrown since the max wait duration is configured lower than the time it should take for the mock to respond. So unexpectedly the request succeeds since it seems the timeout configuration has no effect.
Yes, weirdly enough I can simply disable the Bulkhead and the java.util.concurrent.TimeoutException is thrown and available on the exchange as expected since the mock responds too slowly. I haven't tried to create a Resilience4j-only test using this combination of configurations, so this could perhaps be related to Resilience4j as well? Kind regards Jesper Isaksen -----Original Message----- From: Claus Ibsen <claus.ib...@gmail.com> Sent: 4. oktober 2021 13:43 To: users@camel.apache.org Subject: Re: Resilience4j with Bulkhead and TimeLimiter CAUTION - External Mail Hi So are you saying that calling this http endpoint causes a timeout, but that timeout is not triggered in the Camel route so the exchange fails? And if you turn off bulkhead, then you see such timeout exception on the exchange ? On Mon, Oct 4, 2021 at 1:13 PM Jesper Duelund Isaksen <jesper.duelund.isak...@systematic.com.invalid> wrote: > > Hi Camel users, > > When declaring a Camel Route that uses Resilience4j as a circuit breaker, I > am seeing an issue where configuring a timeout has no effect in case a > Bulkhead is also configured. This happens even though the option > CancelRunningFuture is set to true. > I was wondering if this is unintended or unsupported use of the circuit > breaker? It doesn't seem to be explicitly documented as such though. > > I've created an example project with the route configuration here: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith > ub.com%2Fsys-jdi%2Fcamel-timeout-test%2Fblob%2Fmain%2Fsrc%2Fmain%2Fjav > a%2Forg%2Fproject%2Ftest%2FWireMockRouteBuilder.java&data=04%7C01% > 7Cjesper.duelund.isaksen%40systematic.com%7C2a2ec16a0fdb4c4fabc408d987 > 2c26a1%7C7f6211b17c5c42778403c0ccbd7f0408%7C0%7C0%7C637689445962989713 > %7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6I > k1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=MU86e2IFhU4HXBSloXRk2ldOZ7Bt%2F > cwv41oMrxH6rH0%3D&reserved=0 > > It seems to happen for both Apache Camel 3.11.2 and Apache Camel 3.12.0. > > Kind Regards > Jesper Isaksen -- Claus Ibsen ----------------- https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdavsclaus.com%2F&data=04%7C01%7Cjesper.duelund.isaksen%40systematic.com%7C2a2ec16a0fdb4c4fabc408d9872c26a1%7C7f6211b17c5c42778403c0ccbd7f0408%7C0%7C0%7C637689445962999660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=J9XIjzr6RQowU22meMAqpoLar15tvr8jkNzCRrvveZc%3D&reserved=0 @davsclaus Camel in Action 2: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.manning.com%2Fibsen2&data=04%7C01%7Cjesper.duelund.isaksen%40systematic.com%7C2a2ec16a0fdb4c4fabc408d9872c26a1%7C7f6211b17c5c42778403c0ccbd7f0408%7C0%7C0%7C637689445962999660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=pMT5N%2FJqlbFAh%2F3YPpYVSYgmJbJl4veliotD17q0RH8%3D&reserved=0
