[
https://issues.apache.org/jira/browse/CAMEL-10718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333529#comment-16333529
]
Gajendra kumar jatav commented on CAMEL-10718:
----------------------------------------------
Hi i'm using ThrottlingExceptionRoutePolicy policy to detect availability of a
web service and stop route for some time, but before onExchangeDone called
error handler moves the current message to dead letter queue. I want to avoid
putting messages to DLQ for specific situation which can be handled using
ThrottlingExceptionRoutePolicy.
Is it possible with ThrottlingExceptionRoutePolicy not to put current message
to DLQ where ThrottlingExceptionRoutePolicy needs to take action.
> Route Policy implements circuit breaker pattern to stop consuming from the
> endpoint
> -----------------------------------------------------------------------------------
>
> Key: CAMEL-10718
> URL: https://issues.apache.org/jira/browse/CAMEL-10718
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Mike Barlotta
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 2.19.0
>
>
> Our project recently needed a circuit breaker that stop consuming messages
> from the from endpoint. I noticed that the Camel circuit breakers consumed
> from the endpoint even in the open mode and controlled access to the to
> endpoints on the route.
> Based on a Stack Overflow answer, I created a circuit breaker that will stop
> consuming from the starting endpoint based on exceptions being thrown. It is
> using a RoutePolicy and imitates the existing ThrottlingInflightRoutePolicy
> as well as the CircuitBreakingLoadBalancer.
> This is in the PR 1400
> https://github.com/apache/camel/pull/1400
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
