You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2026/09/02 15:48:00 UTC

[jira] [Created] (ARTEMIS-6223) MQTT clean start can leak durable QoS2 caches

Justin Bertram created ARTEMIS-6223:
---------------------------------------

             Summary: MQTT clean start can leak durable QoS2 caches
                 Key: ARTEMIS-6223
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-6223
             Project: Artemis
          Issue Type: Bug
            Reporter: Justin Bertram
            Assignee: Justin Bertram


When an MQTT client connects requesting a fresh session (i.e., clean session in MQTT 3.1.1 or clean start in MQTT 5.0) the broker must discard all previous session state, including the durable QoS2 packet-id caches used for duplicate detection.

The broker only deletes these caches when the corresponding in-memory cache reference has been lazily loaded. That reference is often {{null}} on a clean-start {{CONNECT}} (e.g. when the durable cache was recovered from the journal after a broker restart, or created by  a different session-state instance for the same client id). In those cases the durable cache is skipped and leaked.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org