[
https://issues.apache.org/jira/browse/CAMEL-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942152#comment-14942152
]
Claus Ibsen commented on CAMEL-9184:
------------------------------------
Yeah my first though would also be for a rejected to be rejecated asap. Wonder
if you would like to dive into the source to see what can be changed?
> Throttler: Rejected message whe rejectExecution=true
> ----------------------------------------------------
>
> Key: CAMEL-9184
> URL: https://issues.apache.org/jira/browse/CAMEL-9184
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.15.3
> Reporter: Arno Noordover
> Fix For: 2.17.0
>
>
> When a message gets rejected and rejectExecution is true, the rejected
> message is still assigned to the new time-slot.
> When you use the throttler to secure against DOS going to the backend a DOS
> can fill up many time-slots.
> I'm not sure whether this behaviour is the expected behaviour. My feeling
> says that the rejected message should not be assigned to a new time-slot.
> Maybe the exception should be raised in the synchronized method that
> determines the starting of a new time-slot.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
