Gary, I use ActiveMQ 5.3.0
Yes, the work-around does work for me.
-Frank-
--
View this message in context:
http://old.nabble.com/Consumer-client-stops-after-failover-tp27778246p28387762.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
If I use the following url
-Durl='failover://(tcp://broker1:61616,tcp://broker2:61616)' I got the
following output:
r...@broker1:/opt/apache-activemq-5.3.0/example # ant topic-listener
-Durl='failover://(tcp://ppst-broker1:61616,tcp://broker2:61616)'
Buildfile: build.xml
init:
compile:
topic-l
t;
> at least it worked when I tested it.
>
> Cheers
> --
> Dejan Bosanac - http://twitter.com/dejanb
>
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
>
>
> On Mon, Mar
Hello world,
I tried out the topic listener example delivered with active mq 5.3.
Without failover, it works very well and waits for incoming messages.
With failover, it stops working after 11 seconds, when no messages arrives.
The same problems occurs with failover with only one broker or with t
Hello everybody,
I'm using a little consumer client (java file attached) to monitor a
message topic. If the broker which the client is connected to does not
fail, everything is ok. If the broker fails, the client tries to connect to
the second broker (the debug says he did!) and then the client s
