[ 
https://issues.apache.org/jira/browse/ARTEMIS-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18063049#comment-18063049
 ] 

ASF subversion and git services commented on ARTEMIS-5798:
----------------------------------------------------------

Commit 31c84c4c39096f26ac96a91f776e3a88ca166aa9 in artemis's branch 
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=artemis.git;h=31c84c4c39 ]

ARTEMIS-5798 MQTT QoS2 unauthorized pub ignored on retry


> MQTT QoS2 unauthorized publish ignored on retry
> -----------------------------------------------
>
>                 Key: ARTEMIS-5798
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5798
>             Project: Artemis
>          Issue Type: Bug
>          Components: MQTT
>    Affects Versions: 2.44.0
>         Environment: Artemis 2.44.0
> Eclipse Paho MQTT Python client 2.1.0
>            Reporter: Tommy Tsim
>            Assignee: Justin Bertram
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> With MQTT 3.1.1, when PUBLISH QoS2 packet failed (custom LoginModule throw 
> ActiveMQSecurityException based on time), the client reconnect with valid 
> credential and resend the same PUBLISH packet. The server ignores and logs:
> {noformat}
> AMQ834009: Ignoring duplicate MQTT QoS2 PUBLISH packet for packet ID client 
> from client with ID XX.{noformat}
> Server session state is not handling the failed PUBLISH packet so PUBLISH 
> packet with the same packet ID no longer be handled.
> Reference:
> https://github.com/apache/activemq-artemis/blob/2.44.0/artemis-protocols/artemis-mqtt-protocol/src/main/java/org/apache/activemq/artemis/core/protocol/mqtt/MQTTPublishManager.java#L209-L212



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to