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

["Justin Bertram (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-6223.
-------------------------------------
    Fix Version/s: 2.57.0
       Resolution: Fixed

> MQTT clean session/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
>            Priority: Major
>             Fix For: 2.57.0
>
>
> 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