> There are no address settings like autoDeleteQueues, autoDeleteCreatedQueues, configDeleteQueues etc. I wonder how could this happen.
Can you invoke the "getAddressSettingsAsJSON" management method on the ActiveMQServerControl [1] passing in "$.artemis.internal.sf.#" as the match and provide the output here? Justin [1] https://activemq.apache.org/components/artemis/documentation/javadocs/javadoc-latest/org/apache/activemq/artemis/api/core/management/ActiveMQServerControl.html#getAddressSettingsAsJSON(java.lang.String) On Thu, Nov 21, 2024 at 3:41 AM Alexander Milovidov <milovid...@gmail.com> wrote: > Hi All! > > We have Artemis cluster with two primary / backups, and it worked normally > before. Suddenly, the cluster queue was undeployed on one of the cluster > nodes during reload of the broker configuration. There was a log message > with event id AMQ224077 Undeploying queue > $.artemis.internal.sf.cluster-name.cluster-node-uuid. > > After this queue was undeployed, the messages which were routed to other > cluster node were unrouted and discarded. > > There are no address settings like autoDeleteQueues, > autoDeleteCreatedQueues, configDeleteQueues etc. I wonder how could this > happen. > The cluster queue was recreated after restart of the cluster connector. > > I don't know the root cause of the problem and we would like to prevent > this situation in the future because it leads to message loss. Is it ok to > make cluster addresses and queues to be configuration-managed on both > cluster nodes? > > ActiveMQ Artemis version is 2.37.0. > > -- > Regards, > Alexander >
