But now I tried it and in the meantime, when both (non-exclusive) diverts are
active, it duplicates the messages. So unfortunately, that's not a valid
option.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
That's brilliant! Thank you. :-)
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hello,
My AMQ Artemis broker is failing to start with the nullPointerException
"couldn't find factory for type=0". I am seeing this after having just
upgraded from 2.11.0 to 2.12.0, previously the broker was able to start up
successfully. I am unsure whether this issue is being caused by
Hi,
I guess you don't want to leave the address without your divert for the time
you need to invoke `destroyDivert` and `createDivert` again. If that's the
case, you could execute the following steps:
1) create the new divert with a temporary name
2) destroy the old divert
3) create the new
Hello.
I'm working on an automatized broker configuration in a way that it's
supposed to fully reflect the workflow. What I struggle with though is
reconfiguration of a divert. The source code of 2.12.0 states this:
This basically means that a divert will be deployed only if there's no
binding
