Hi Jason If the messages are persistent, they are stored in the storage (KahaDB for instance), and when a failover happens, you should be able to browse and see the messages payload.
Can you share more details about your messages ? What store are you using? Regards JB On Tue, Mar 10, 2026 at 1:15 PM Jason Jackson <[email protected]> wrote: > Using ActiveMQ Classic 6.2.1 in a Master-Slave environment on two > different hosts. > > The Master-Slave and failover is working exactly like it should be. > > I have observed the following. > > When the broker is running on HOST1 and is processing data/messages in > QUEUE1; for whatever reason it fails over to HOST2. When the failover > occurred there was data/messages in QUEUE1. When I access the broker on > HOST2 I can see that QUEUE1 contains data/messages but I noticed that I am > not able to see the data/messages, I just see there is a queue depth of X. > If I fail the broker back to HOST1 I am able to see the messages. > > I suspect the reason I am not able to see the data/messages when the > broker fails over is due to the message header/information containing > information from HOST1 and now that it is running on HOST2 there is an > issue and/or it does not recognize them. > > I have two questions. > > > 1. > Is there a setting that can be enabled where the messages are visible on > HOST2 when a failover occurs? > 2. > Even though I can not see the messages would they still be processed on > HOST2 even though there may be details from HOST1 in the data/messages? > > Thank you. > > > Jason > > >
