[
https://issues.apache.org/jira/browse/AMQ-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570193#comment-17570193
]
Marcus Hunger commented on AMQ-6575:
------------------------------------
Hash this been addressed?. It still seems to be an issue in ActiveMQ Classic
5.17.4
Retained messages are lost when the broker is restarted. Will this be addressed
or is this level of MQTT compatibility out of scope for ActiveMQ?
> Retained messages not persisted? (MQTT)
> ---------------------------------------
>
> Key: AMQ-6575
> URL: https://issues.apache.org/jira/browse/AMQ-6575
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, MQTT
> Affects Versions: 5.14.3
> Reporter: Stefan Nilsson
> Priority: Major
>
> *Issue*
> Retained message is not persisted (after restart?)
> *Steps to reproduce*
> # Client *c1* connects and publishes a message *m1* to topic *t1* with
> retain: *true* and QoS: *2*. Client then disconnects.
> # Client connect (with same clientId or different, both works) and *c1*
> subscribes to *t1*. *c1* recieves *m1*.
> However, if the broker is restarted and *step 2* is re-run, the *m1* is never
> recieved.
> Shouldn't a retained message with QoS-2 be persisted and send to clients even
> after restart?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
