You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Miroslav Minárik (JIRA)" <ji...@apache.org> on 2018/07/20 12:27:00 UTC
[jira] [Created] (ARTEMIS-1983) Usage of STOMP NACK command leads
to data loss
Miroslav Minárik created ARTEMIS-1983:
-----------------------------------------
Summary: Usage of STOMP NACK command leads to data loss
Key: ARTEMIS-1983
URL: https://issues.apache.org/jira/browse/ARTEMIS-1983
Project: ActiveMQ Artemis
Issue Type: Bug
Components: STOMP
Affects Versions: 2.6.2
Reporter: Miroslav Minárik
Assignee: Justin Bertram
Implementation of NACK command of STOMP protocol v1.1 and 1.2 causes message(s) loss. Bug is in source code in apache-artemis-2.6.2/artemis-protocols/artemis-stomp-protocol/src/main/java/org/apache/activemq/artemis/core/protocol/stomp/v11/StompFrameHandlerV11.java in this part:
{code}
public StompFrame onNack(StompFrame request) {
//this eventually means discard the message (it never be redelivered again).
//we can consider supporting redeliver to a different sub.
return onAck(request);
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)