Hi
No its better to use the built-in timeouts you have from the JMS
component (such as request timeout if doing request/reply) and the JMS
clients such as from ActiveMQ etc. Then you should not need to use the
timeout setting from receipinent list which is a fallback way and in
this situation adds
Thanks, Claus. This is great. To mitigate the possible issues from
dangling threads, would you recommend that I use my own executorServiceRef
that handles the timeouts gracefully?
On Tue, Jun 28, 2016 at 9:22 AM, Claus Ibsen wrote:
> Hi
>
> It depends if sending to those destinations fails wit
Hi
It depends if sending to those destinations fails with an exception,
then the aggregate method receives an exchange with the caused
exception.
If you use timeout, then the aggregate method is not invoked, but you
can implement the TimeoutAwareAggregationStrategy to have a special
callback from
Hello. In my application, I have a list of recipients, but at any time
when I send messages to this list of recipients, it is possible that they
may be unreachable. I want to aggregate responses, but how will the
aggregation count be affected by unreachable destinations in the list?
Thanks,
Stev
