I'm currently running a cluster, and I do see it is automatically failing
over to other nodes in the cluster.
But I am trying to test the case where all brokers in the cluster is down (
or in other words the cluster is down ),
I'm hoping both the producer and the client won't just die but keep on
On Thu, Nov 18, 2010 at 5:10 PM, Tim Chen wrote:
> Hi all,
>
> I wonder what's the best way to handle reconnect to the broker when broker
> is unavailable (network is down / broker crashed, etc) using Java JMS
> client
> to C++ broker?
>
Are you running a cluster or is it a bunch of standalone b
Is the failover for a cluster or just to brokers.
For a cluster, the heartbeat etc need to be setup and the rest is automatic
from the failover exchange.
If just two brokers, then the connection URL needs to be used.
Carl.
On 11/21/2010 03:30 PM, Tim Chen wrote:
Anyone?
Tim
On Thu, Nov 1
Hi Tim,
The Java client uses the connection URL to control failover, but I'm not
sure whether/how that is honoured by the C++ broker. It also defaults on
trunk to use a NoFailover policy.
Rajith - I think you might have the most up-to-date knowledge on the Java
client failover on trunk, do you ha
Anyone?
Tim
On Thu, Nov 18, 2010 at 2:10 PM, Tim Chen wrote:
> Hi all,
>
> I wonder what's the best way to handle reconnect to the broker when broker
> is unavailable (network is down / broker crashed, etc) using Java JMS client
> to C++ broker?
>
> Currently when using the JMS client when the
Hi all,
I wonder what's the best way to handle reconnect to the broker when broker
is unavailable (network is down / broker crashed, etc) using Java JMS client
to C++ broker?
Currently when using the JMS client when the broker is killed, a runtime
exception ( ConnectionException ) is thrown inter
