camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (CAMEL-3159) Aggregator EIP - Add option to ignore timeout completed
Date Sun, 26 Sep 2010 13:47:40 GMT

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

Claus Ibsen reassigned CAMEL-3159:
----------------------------------

    Assignee: Claus Ibsen

> 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
>
> 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.


Mime
View raw message