>From what I have learned from others, this problem is present in
ActiveMQ-5.4.2-fuse-01-00 and it only happens when you try to set up
failover on a networkConnector with a single duplex remote address. If more
than one remote address is set up then it works fine.
--
View this message in context
Do you have any evidence that leaving the static off works? I have used the
full static:(failover:(tcp...) before in ActiveMQ 5.3.2 and it works there.
Why would it not work here?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-5-4-2-failover-not-working-correctl
This link may give some info:
https://issues.apache.org/jira/browse/AMQ-2764 AMQ-2764
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-5-4-2-failover-not-working-correctly-tp3341700p3341954.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Am I using it in wrong way?
My two ActiveMQ Brokers listening on 61616, 62616 (Openwire tcp URI)
And My application has a failover URI like this
amq.broker.url=failover:(tcp://0.0.0.0:61616,tcp://0.0.0.0:62616)?randomize=false&jms.prefetchPolicy.all=1
Am I using it in a efficiant way...Can y
Hi,
That is working for me fine. I have little different scenario (minus network
connectors)
I have two ActiveMQ-5.4.2 installed on my local machine as different windows
XP services, For Persistence Both Pointing same Oracle schema and I started
one by one.
The second one is waiting for a lock
Billy,
You might want to try with just the failover: protocol and leave out the static
failover:(tcp://host1:port1,tcp://host2:port2...)
--- On Tue, 3/8/11, billy wrote:
From: billy
Subject: ActiveMQ-5.4.2 failover not working correctly
To: users@activemq.apache.org
Date: Tuesday, March 8, 20
I didn't see the network connections that I pasted in so let me type them in
here:
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-5-4-2-failover-not-working-correctly-tp3341672p3341691.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.