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

Justin Bertram updated ARTEMIS-1983:
------------------------------------
    Description: 
The STOMP [1.1|https://stomp.github.io/stomp-specification-1.1.html#NACK] & 
[1.2|https://stomp.github.io/stomp-specification-1.2.html#NACK] specifications 
state:

bq. NACK is the opposite of ACK. It is used to tell the server that the client 
did not consume the message. The server can then either send the message to a 
different client, discard it, or put it in a dead letter queue. The exact 
behavior is server specific.

Artemis discards the message, but ActiveMQ 5.x makes the message available for 
redelivery or placement on a DLQ.  Artemis' behavior should be compatible with 
5.x for migrating clients.

  was:
The STOMP 1.1 & 1.2 specifications state:

bq. NACK is the opposite of ACK. It is used to tell the server that the client 
did not consume the message. The server can then either send the message to a 
different client, discard it, or put it in a dead letter queue. The exact 
behavior is server specific.


> 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
>
> The STOMP [1.1|https://stomp.github.io/stomp-specification-1.1.html#NACK] & 
> [1.2|https://stomp.github.io/stomp-specification-1.2.html#NACK] 
> specifications state:
> bq. NACK is the opposite of ACK. It is used to tell the server that the 
> client did not consume the message. The server can then either send the 
> message to a different client, discard it, or put it in a dead letter queue. 
> The exact behavior is server specific.
> Artemis discards the message, but ActiveMQ 5.x makes the message available 
> for redelivery or placement on a DLQ.  Artemis' behavior should be compatible 
> with 5.x for migrating clients.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to