Thank you.
On Sat, Jun 18, 2016 at 5:06 AM Tim Bain wrote:
> Because "randomize=false", local1 will always be tried first, and local2
> will be tried only if local1 is unavailable.
>
> I'm not sure what the answer to your second question is, and unfortunately
> I don't have the ability right now
Because "randomize=false", local1 will always be tried first, and local2
will be tried only if local1 is unavailable.
I'm not sure what the answer to your second question is, and unfortunately
I don't have the ability right now to read the FailoverTransport source
code to find out. Though of cour
Keep in mind that which library JARs you need depends on which lines of the
source code get executed I your specific application. Chris's approach is
the safe one, because it includes everything you might possibly need
without being as bug as the uber-JAR and it's future-proofed as
dependencies ch
Christian, that's great news, thanks for sharing.
Since this feels like a post that people may be referring back to, there
are a couple things I think are worth adding.
If DLQ'ed messages are the only long-lived ones, I would expect a similar
result from using mKahaDB with one KahaDB for normal d
