You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/09/26 16:32:40 UTC

[jira] Resolved: (CAMEL-3159) Aggregator EIP - Add option to ignore timeout completed

     [ https://issues.apache.org/activemq/browse/CAMEL-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-3159.
--------------------------------

    Fix Version/s: 2.5.0
       Resolution: Fixed

trunk: 1001436.

> Aggregator EIP - Add option to ignore timeout completed
> -------------------------------------------------------
>
>                 Key: CAMEL-3159
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3159
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.5.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Aggregator-Howto-remove-from-persistency-tp2852702p2852702.html
> > I was thinking about something like a removeOnTimeout (default=false of
> > course) that would use the existing completionTimeout attribute but change
> > its behavior to remove the aggregated message instead of publishing it.
> > --
> Yeah I can kinda see an use case for this. You are using the timeout
> as a last resort to just say hey we could not aggregate this in lets
> say 4 hours.
> So lets just ignore the message.
> Having an option on the aggregate to just auto discard those message
> on timeout would help there to avoid the CBR and checking yourself.
> Just wondering if this is a use case others use? Its still kinda
> dangerous to discard messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.