When an Artemis broker starts for the first time it creates a UUID and persists it to the journal and that is what is broadcast around the cluster to uniquely identify it. If you happened to have copied one instance to another (e.g. to save yourself the head-ache of configuring the XML) and include the journal by accident this warning will be printed with the broker joins the cluster. To correct the issue just stop the broker, delete the journal directory, and restart. Of course, any messages in the journal will be lost, but I'm guessing there aren't any messages in there since you're just getting started and hit this issue.
As far as the "activemq.bak" directory goes...Artemis doesn't use a directory with that name so I have no idea where that came from or what it is for. Let me know how it goes. Justin On Thu, Jun 7, 2018 at 11:38 AM, alexald <alexaldana10...@gmail.com> wrote: > I am having an issue in our cluster. There are two nodes that have the same > node id. I removed the activemq directory in the node showing this warning: > > AMQ212034: There are more than one servers on the network broadcasting the > same node id. You will see this message exactly once (per node) if a node > is > restarted, in which case it can be safely ignored. But if it is logged > continuously it means you really do have more than one node on the same > network active concurrently with the same node id. This could occur if you > have a backup node active at the same time as its live node. > nodeID=c74ac119-8429-11e7-a2b6-a77a78b916a7 > > But the issue with the same node id still exists. I was not sure what the > activemq.bak is for and if I need to remove it to fix my issue. > > Thank you. > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
