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/10 16:15:00 UTC
[jira] [Updated] (ARTEMIS-6241) Mitigate potential QoS 2 races
[ https://issues.apache.org/jira/browse/ARTEMIS-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram updated ARTEMIS-6241:
------------------------------------
Summary: Mitigate potential QoS 2 races (was: Handle theoretical QoS 2 race)
> Mitigate potential QoS 2 races
> ------------------------------
>
> Key: ARTEMIS-6241
> URL: https://issues.apache.org/jira/browse/ARTEMIS-6241
> Project: Artemis
> Issue Type: Bug
> Components: MQTT
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{MQTTPublishManager}} tracks in-flight QoS2 packet IDs in a durable duplicate ID cache to detect retransmitted PUBLISH packets. Access to this cache is guarded inconsistently, i.e.:
> * {{sendToQueue()}} (which checks for and adds new packet IDs) synchronize on a private lock object
> * {{handlePubRel()}}, {{handlePubRec()}}, {{handlePubComp()}}, and {{handlePubAck()}} (which remove packet IDs) synchronize on the enclosing {{MQTTPublishManager}} instance (i.e. {{this}}).
> Because these are two different monitors, they provided no actual mutual exclusion between adding and removing entries from the same cache.
> This race is deemed "theoretical" because it would not be triggered by any client adhering to the MQTT specification. Nevertheless it should be addressed.
--
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