for my personal view,
1, if you want to impl some requirement like ‘offline message’ for those never
online user
AMQ doesn’t support that. The consumer must connect broker at least
once as durable subscriber, then he can receive offline msg afterwards even
after he offline and then online again.
2, MQTT only support topic
As I know ,it’s by design.
3, Repeat message received
in MQTT client (3rd library), set the Qos = 2, after our testing, only
one message will be received.
William
> On Jun 17, 2015, at 10:21 PM, Tim Bain <tb...@alumni.duke.edu> wrote:
>
> How many subscriptions do you see for that topic via JConsole? If you see
> more than one, that's your problem and you need to figure out why.
>
> If you see only one subscription, what happens to the enqueue count and
> dequeue count and dispatched count when you reconnect the consumer? I'd
> expect them all to be equal (or nearly so) when you disconnect; do any of
> them increase when you reconnect? If so, which ones?
>
> Tim
>
> On Wed, Jun 17, 2015 at 6:49 AM, SummerScent <scent.o.sum...@gmail.com>
> wrote:
>
>> Thank you!
>>
>> I also create the same subscription name for each topic.
>>
>>
>>
>> --
>> 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-tp4697874p4697891.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
