I'm at a bit of a loss. Your expectation that a durable subscriber should only get delivered those messages it hasn't already received is correct, so there's probably a bug here. I'd like you to submit a bug in JIRA along with your broker config and client code and a description of the behavior (creating a durable subscriber from the web console, etc.).
But before we do that, there's one other thing I want you to check. Please use JMX (JMX != web console, use JConsole or your favorite JMX viewer) to confirm that for your topic only one subscriber exists, that the DequeueCount really is going up (not just the DispatchCount), and that all information about the subscriber is the same from one re-connection to the next. If all of those check out, then there's a bug and you should submit a JIRA entry. BTW, are only the messages from before the first connection being retransmitted, or all messages? That is, if you send messages 1-5 before the first connection, 6-8 while you're connected the first time, and 9-10 while you're disconnected, do you get 1-10 when you reconnect or only 1-5 and 9-10? Knowing that might help someone track down what that root cause is. Tim On Wed, Jun 17, 2015 at 10:37 PM, SummerScent <scent.o.sum...@gmail.com> wrote: > Hi Tim, > > Here is an example of the dispatched queue, enqueue, dequeue count. > > > <http://activemq.2283324.n4.nabble.com/file/n4697942/subscriber.png> > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Active-MQ-5-11-1-MQTT-Message-is-automatically-sent-to-subscriber-when-it-is-connected-tp4697874p4697942.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
