You edited the Broker in slave and it became live ?
If you edited live the only thing I can think of wasn’t a bug fixed in 2.3
where queues would be removed if edited. But I don’t see it was the case
here.
On Sat, Oct 21, 2017 at 12:13 AM Dan Langford wrote:
> I am just getting back from back
I am just getting back from back to back tech conferences. thanks for the
follow up.
i attached a broker0.xml (master, :61616, :5672, :8161) and broker1.xml
(slave, :61617, :5673, :8162)
when i start broker0 and broker1 i see that broker1 announces itself as the
backup. also both broker show Artem
Any progress here?
Justin
On Thu, Sep 21, 2017 at 3:51 PM, Dan Langford wrote:
> a quick note and then i will work on providing a more reproducible use set
> of artifacts.
>
> > How did you test that?
>
> Three things i notice. 1) in the JMX console (viewed via Hawtio/jolokia
> api in 2.1, an
a quick note and then i will work on providing a more reproducible use set
of artifacts.
> How did you test that?
Three things i notice. 1) in the JMX console (viewed via Hawtio/jolokia
api in 2.1, and the skinned version of such in the new 2.3 console [very
nice BTW]) the slave will typically N
The only scenario I can think here on the loss of address/queues , noting that
somehow your slave is thinking it can active as master (aka acceptors start up)
is that auto-delete-queues/auto-delete-address is kicking in (which default is
true I believe) as it deletes queue on no subscription and
I’ve just tested manually (in a HA setup) that if you set delete policy to OFF
which by default it is set to OFF, then queues and address do not get
undeployed on reload. Eg queues and addresses if created in GUI or CLI remain.
Only if you change/override that to FORCE would it remove an addres
> If I make any change at all to the slave broker.xml file the
"configuration reload" feature takes effect and starts/enables the
acceptors on the Slave.
How did you test that? Looking at the code it appears the configuration
reload logic shouldn't touch the acceptors. Also, I just tested this o
Quick Summary: If I make any change at all to the slave broker.xml file the
"configuration reload" feature takes effect and starts/enables the
acceptors on the Slave. This causes the slave to stop backing up the master
and start accepting its own connections. also address and security settings
that
