[
https://issues.apache.org/jira/browse/CAMEL-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105967#comment-13105967
]
Claus Ibsen edited comment on CAMEL-4097 at 9/16/11 9:44 AM:
-------------------------------------------------------------
An easier solution could be to just keep track on the
inProgressCompleteExchanges and wait until it reaches 0, then you know all the
flushed exchanges is done. Then when its zero, you can continue the regular
stopping code.
was (Author: davsclaus):
An easier solution could be to just keep track on the
inProgressCompleteExchanges and wait until it reaches 0, then you know all the
flushed exchanges is done.
> Add option on aggregation to flush on shutdown
> ----------------------------------------------
>
> Key: CAMEL-4097
> URL: https://issues.apache.org/jira/browse/CAMEL-4097
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Ben O'Day
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: CAMEL-4097.patch
>
>
> We may want to add options to stateful EIPs such as aggregator/resequencer
> that they should flush on shutdown. People who dont use a persistent store
> would loose the in-memory partly aggregated exchanges.
> See nabble
> http://camel.465427.n5.nabble.com/Aggregator-completeOnShutdown-tp4423774p4423774.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
