What I mean is that you're using a fault-tolerant replicated datastore, which means that the message can be considered successfully received by the broker even if it's not written to all of the replicated stores. By shutting down all but one store and expecting that the messages will be there, you're requiring n3 to have successfully received the messages, but you've not described anything yet that proves that that actually happened. So the first step is to prove that n3 actually got the messages; if it didn't, the behavior you saw is expected and there's no bug.
I've never run LevelDB, so I don't have much direct experience here, but I'd expect that you'd see files written to the data directory if n3 is getting the messages. The web console won't tell you anything useful here, because it doesn't show any information about replication in a replicated datastore. Tim On Sun, Jun 12, 2016 at 3:19 PM, achint...@gmail.com <achint...@gmail.com> wrote: > Can you explain bit in details what do you mean by "n3 is actually > receiving > messages"? Or how I can test that n3 is receiving the messages or not. In > ActiveMQ web console I see the Pending message is 0. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Message-is-lost-tp4712859p4712913.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
