Hi Tim
I seems to work better but now I've got message reading issues with my Java app.
I'll fix my readers before testing further the AMQ.
thanks
marc
Le 28/01/2016 15:17, Tim Bain [via ActiveMQ] a écrit :
No, I meant that I think the amidala broker shouldn't have a
networkConnector to amidala, a
I've checked the logs, I see no self connection.
I've changed TTL to 4, but i'm at home, i'll test tomorrow.
you're right, i'm not sure msf01 and ms02 are used to dequeue messages, i have
to check the logs next time.
i thought they were used because they are very close to the messages readers
(lo
No, I meant that I think the amidala broker shouldn't have a
networkConnector to amidala, and same for the other three.
You can't consume messages that have been forwarded to a second broker from
clients on a third broker because the default networkTTL for
networkConnectors is only 1. Increase it
Hi Tim
yes i'm having the same config (except the broker name change).
when you say not not send to itself you mean for example system write :
Regarding what happened:
I've posted some messa
Are you using this config file for all four brokers? It looks like you're
having each broker connect not only to the other three but also to itself;
is that true? If so, I'm not sure what happens if a broker connects to
itself, but I'd try eliminating that from the configuration and see if it
cha
Hi Tim,
Thanks a lot for your response.
I was on another project, that's why I was sooo long to answer.
I now understand well that the message is passed from one server to another.
I have difficulties to put all pieces together.
Unfortunately for me all leads to ActiveMQ FAQ, and i keep confused.
Why are you only forwarding one destination per networkConnector, and a
different one in each case? And what destination are you publishing to?
It sounds like you believe that you have a master/slave cluster (you say
"cluster1 is the active machine"), but that's not true. What you actually
have
