This seems like an environmental issue of some kind. The error message clearly states:
BROKER_PROD_1, no longer able to keep the exclusive lock so giving up being a master So, the broker lost its exclusive lock which means it will shut itself down to avoid split brain. This lock is what the master and the slave compete for to ensure only one broker is active at a time. You should ensure that the broker is able to maintain its lock or this will happen. Justin On Wed, Nov 27, 2024 at 2:22 AM GIRONA Pierre <pierre.gir...@sodiaal.fr.invalid> wrote: > Hello, > > > > I have a problem with activeMQ. My configuration is in cluster mode and > once a month or so, the master node reboots by itself. > > Have you ever had this problem? > > > > You can find attached the log files of each nodes. The node 1 restart on > 2024-11-14 at 17:21:21,946 with this error : > > > > BROKER_PROD_1, no longer able to keep the exclusive lock so giving up > being a master | org.apache.activemq.broker.LockableServiceSupport | > ActiveMQ JDBC PA Scheduled Task > > > > Thanks for your help. > > > > [image: cid:image001.png@01D9E63C.D620F290] > > [image: Description : ligne_bleue] > > > *Pierre GIRONA *Référent Middleware > > Centre de compétences DIAE - Data, Intégration & Architecture d’Entreprise > DSI Groupe > > > > 78 rue de la Villette 69425 Lyon Cedex 03 > > Mob. +33 (0)6 73 33 18 50 > > E-mail : pierre.gir...@sodiaal.fr - web : www.sodiaal.fr > > Avant d'imprimer, merci de penser à l'environnement. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org > For additional commands, e-mail: users-h...@activemq.apache.org > For further information, visit: https://activemq.apache.org/contact >
