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