[
https://issues.apache.org/jira/browse/DISPATCH-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322488#comment-15322488
]
ASF subversion and git services commented on DISPATCH-366:
----------------------------------------------------------
Commit 7279a153b7f04196bcba2876d2e1d7ff2a003919 in qpid-dispatch's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=7279a15 ]
DISPATCH-366 - Use modified+delivery-failed for released messages whose
deliveries are in doubt.
> When delivery fails the router sends the RELEASED disposition, not MODIFIED
> ---------------------------------------------------------------------------
>
> Key: DISPATCH-366
> URL: https://issues.apache.org/jira/browse/DISPATCH-366
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
> Affects Versions: 0.6.0
> Reporter: Ken Giusti
> Assignee: Ted Ross
> Priority: Blocker
> Fix For: 0.7.0, 0.6.1
>
>
> The router does not properly distinguish between a delivery failure and
> undeliverable.
> In the case of a delivery failure - where the router cannot ensure that the
> message wasn't consumed - the router must send back the MODIFIED terminal
> disposition with the delivery-failed flag set. This is necessary as the
> sender must increment the message's delivery-count if it retransmits.
> In the case of an undeliverable message - where the router cannot forward a
> message to the destination - the router must send back the RELEASED terminal
> disposition. RELEASED informs the sender that the message was not acted
> upon. The sender must not increment the message's delivery-count if it
> retransmits.
> Currently the router uses RELEASED in both these cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
