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

Timothy Bish updated ARTEMIS-794:
---------------------------------
    Description: 
The Modified outcome when sent has certain constraints placed on how the broker 
should handle it.  If the outcome indicates the delivery failed the remote must 
increment the delivery count, otherwise it should not.  If the outcome 
indicates that the message is "undeliverable here" than the remote must not 
send the message back to the modifying link.  (Note that in 5.x we treat the 
undeliverable here value as a cause to DLQ the message in order to ensure we 
don't redeliver it again to the link that modified it)

The Rejected Outcome is meant to be a terminal outcome and the message should 
transition to the Archived state which would amount to be sent to the DLQ in 
Artemis.  


  was:
The Modified outcome when sent has certain constraints placed on how the broker 
should handle it.  If the outcome indicates the delivery failed the remote must 
increment the delivery count, otherwise it should not.  If the outcome 
indicates that the message is "undeliverable here" than the remote must not 
send the message back to the modifying link.  

(Note that in 5.x we treat the undeliverable here value as a cause to DLQ the 
message in order to ensure we don't redeliver it again to the link that 
modified it)


> AMQP: Modified and Rjected Outcomes are not being handled correctly
> -------------------------------------------------------------------
>
>                 Key: ARTEMIS-794
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-794
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>          Components: AMQP
>    Affects Versions: 1.4.0
>            Reporter: Timothy Bish
>            Priority: Blocker
>
> The Modified outcome when sent has certain constraints placed on how the 
> broker should handle it.  If the outcome indicates the delivery failed the 
> remote must increment the delivery count, otherwise it should not.  If the 
> outcome indicates that the message is "undeliverable here" than the remote 
> must not send the message back to the modifying link.  (Note that in 5.x we 
> treat the undeliverable here value as a cause to DLQ the message in order to 
> ensure we don't redeliver it again to the link that modified it)
> The Rejected Outcome is meant to be a terminal outcome and the message should 
> transition to the Archived state which would amount to be sent to the DLQ in 
> Artemis.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to