You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/10/04 11:46:30 UTC
[jira] [Assigned] (CAMEL-9184) Throttler: Rejected message whe
rejectExecution=true
[ https://issues.apache.org/jira/browse/CAMEL-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-9184:
----------------------------------
Assignee: Claus Ibsen
> Throttler: Rejected message whe rejectExecution=true
> ----------------------------------------------------
>
> Key: CAMEL-9184
> URL: https://issues.apache.org/jira/browse/CAMEL-9184
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.15.3
> Reporter: Arno Noordover
> Assignee: Claus Ibsen
> Fix For: 2.16.0
>
> Attachments: CAMEL-9184__Rejection_of_message_should_not_fill_new_timeslot.patch
>
>
> 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)