The problem is resolved in 5.6-SNAPSHOT with the auditNetworkProducers flag
so I'll take another look at my backport.
Thanks,
Bruce
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AMQ-5-5-1-Duplicate-Messages-After-Network-Outage-and-Broker-Restart-tp4520697p4526378.html
S
After resolving my previous problem with the a network connector reconnection
after a network outage I am now seeing duplicate messages being delivered
from a queue. The situation is this:
I have a spoke instance which has a network connector to a hub instance.
For testing purposes I have them r
Thanks. I was simulating our more complicated production environment which
uses hot standby instances. I assume this would be the right URL to use for
load balancing against two instances each with a hot standby?
static:(failover:(tcp://hub1:61001,tcp://hub2:62001)?updateURIsSupported=false&maxR
This appears to be similar situation to what is described in AMQ-3277. I
have added a maxReconnectAttempts=1 to my network connection URL and have
yet to see a reconnection failure.
maxReconnectAttempts=1*)"
name="network-connector"
networkTT
A bit more info after a bit of investigation... It appears that Network
Connector is created, but not active. When it works, I see this in the log:
[org.apache.activemq.transport.failover.FailoverTransport] : Connection
established
[org.apache.activemq.transport.failover.FailoverTransport] : Suc
Thanks for the reply. I tried taking the // out so I'm now using:
but it failed on the second run of my test.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AMQ-5-5-1-Message-Routing-Doesn-t-Resume-After-Network-Outage-tp4516807p4517077.html
Sent from the Activ
I have been seeing a problem where messages from a spoke instance of AMQ does
not always continue to send messages to a central hub instance using its
network connector after a network outage. The network connector has
apparently reconnected, but the hub/network connector is no longer listed as
a
