You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2018/07/21 00:55:00 UTC
[jira] [Updated] (ARTEMIS-1983) STOMP NACK behavior incompatible
with 5.x
[ https://issues.apache.org/jira/browse/ARTEMIS-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram updated ARTEMIS-1983:
------------------------------------
Summary: STOMP NACK behavior incompatible with 5.x (was: Usage of STOMP NACK command leads to data loss)
> STOMP NACK behavior incompatible with 5.x
> -----------------------------------------
>
> 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
> Priority: Major
>
> 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)