That seems like a restricted solution that the Consumer should be a servlet.
May I know why?
What I have is a standalone Consumer (for testing purposes). Not sure how
the Production systems are, but the standalone Consumer dies as soon as the
Master is down. I have been looking for a solution to t
Consumer can do failover in web project. Consumer should be a servlet! You
can have a try!
On Tue, Aug 21, 2012 at 2:38 AM, joesan [via ActiveMQ] <
ml-node+s2283324n4655327...@n4.nabble.com> wrote:
> Did you find a solution to this? I have more or less the same issue. My
> Producer can fail-over
Did you find a solution to this? I have more or less the same issue. My
Producer can fail-over but my Consumer dies as soon as the master dies.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/master-slave-consumer-can-not-failover-tp4653639p4655327.html
Sent from the Acti
broker uri: failover:(tcp://localhost:61616, tcp://localhost:61617)
but the problem still occurs...
my configuration is right, the exception indicates that the client fail from
61616, try to reconnect 61617
--
View this message in context:
http://activemq.2283324.n4.nabble.com/master-slave-cons
Your failover url should read:
String brokerUrl = "failover:(tcp://hostA:61616,tcp://hostB:61617)";
Please try that.
Torsten Mielke
tors...@fusesource.com
tmie...@blogspot.com
On Jun 29, 2012, at 1:24 PM, mickhayes wrote:
> This bit:
>
> /String brokerUrl = "failover:(tcp://hostA, tcp://ho
This bit:
/String brokerUrl = "failover:(tcp://hostA, tcp://hostB)";
needs to include the port number 61617.
Does it?
-
Michael Hayes B.Sc. (NUI), M.Sc. (DCU), SCSA SCNA
--
View this message in context:
http://activemq.2283324.n4.nabble.com/master-slave-consumer-can-not-failover-tp46536
Thanks for you answer!
*In my environment, hostA on port 61616, hostB on 61617.*
When master down, slave becomes master. Producer can failover, but consumer
not with the same configuration.
String brokerUrl = "failover:(tcp://localhost:61616,tcp://localhost:61617)";
What troubles me is why the
What's the consumer's logging output?
When you shut down the master on hostA, the consumer will loose its connection
to the broker and should try to reconnect. It will try both of the tcp urls in
your list until it reconnects.
Also, can you confirm that your slave broker starts up just fine on
