At this point what would really be helpful is some test code that shows what is going on. Otherwise it is hard to understand the real problem and the intended use case here.
On Mon, Jun 22, 2015 at 9:00 AM, Tim Bain <tb...@alumni.duke.edu> wrote: > If I understand correctly, what you're saying is that the messages that > were being redelivered each time were doing so because they'd been sent > with the RETAIN flag > <http://www.hivemq.com/mqtt-essentials-part-8-retained-messages/> set, > which (according to that page) means that they are supposed to be delivered > to a subscriber when it subscribes. Based on that page, only the last > retained message should be delivered when the subscriber subscribes; was > that the behavior you were seeing, or were you getting more than one > message per subscriber each time? > > I don't see anything in that description that says that a subscriber should > receive the message at any time other than when it *subscribes*, though > maybe the correct implementation is to send the latest message on each > reconnect and the page is just misleading. Do you have further information > about the proper behavior of MQTT on that point? > > Tim > > On Sun, Jun 21, 2015 at 9:52 PM, SummerScent <scent.o.sum...@gmail.com> > wrote: > > > Hi Tim, > > > > Thanks so much for your consideration. > > > > Last time the subscriber automatically receive the message when connected > > is > > because I publish the message with RETAINED flag. > > > > But I have the trouble with the durable subscription created by Web > > Console: > > Some durable subscriptions are working well with offline messages (It > keep > > all offline message as Pending state and when the actual subscriber is > > connected, all these messages are delivered to it). But some durable > > subscriptions are not working ( they keep the offline message as Pending, > > but they does not deliver these message to the actual subscriber when it > is > > connected). > > > > I don't know why the ActiveMQ remove all the durable subscription when it > > is > > re-started. I mean that: My actual subscriber is already connected to > > ActiveMQ and subscribe some durable topic with clean Session is FALSE > but > > when ActiveMQ restart, it remove all these durable subscription. That's > why > > I need to create some durable topic subscription when the ActiveMQ is > > started. > > > > Thanks so much! > > > > > > > > > > -- > > 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-tp4697874p4698036.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > -- -- Tim Bish
