Have you increased the messageTTL to allow more than 1 broker-to-broker
forward? See http://activemq.apache.org/networks-of-brokers.html for
details of that networkConnector property.
Tim
On Sun, Jul 26, 2015 at 7:04 PM, Cadmean wrote:
> I just found by setting "duplex=true" connection for eve
I just found by setting "duplex=true" connection for every broker, some
channels between brokers are blocked.
So here is my problem again:
I have brokers A,B,C,D and only 1 consumer connected to A, according to the
network connections, all the messages from B,C and D should be forwarded to
A and
If all brokers connect to all other brokers using duplex="false", then you
have a complete graph and messages can pass from any broker. So I don't
think duplex has anything to do with your problem. (Though if you have a
duplex connection from every broker to every other broker, then there are
two
This problem has been solved by :
1. setting F5 load balancer as : least connection & session keeping
2. setting networkConnector as : remove localhost, duplex="true",
dynamicOnly="true"
3. setting destination policy as : replayWhenNoConsumer="true"
I think the main problem of my question is
Did you read and apply the Stuck Messages section of the page you linked?
Also, is your F5 configured to make clients sticky to a particular broker?
ActiveMQ is not like a web server where each request is stateless; you
can't bounce a connected client between brokers and have it behave
correctly.
