Non-durable topic subscriptions have that issue no matter what - lose the connection and all unconsumed messages are dropped. And all messages published while disconnected are also missed.
Keep in mind too that Topics do not persist messages themselves in ActiveMQ; only durable subscriptions lead to persistence of the messages. Migrating from one broker to another, or even upgrading a single broker, non-durable Topic subscriptions need a solution outside the broker. Of course, given their nature, I hope the application is written in such a way that missing those messages is not critical since otherwise the application is going to have major problems (due to message loss) when there are hiccups in the network. -- View this message in context: http://activemq.2283324.n4.nabble.com/Data-Migration-from-KahaDB-to-LevelDB-tp4692615p4693034.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.