[ 
https://issues.apache.org/jira/browse/DISPATCH-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635992#comment-16635992
 ] 

ASF subversion and git services commented on DISPATCH-1081:
-----------------------------------------------------------

Commit 6689d5f1d6dc343ab0482befcf3286479aef2e04 in qpid-dispatch's branch 
refs/heads/master from [~bhardest]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=6689d5f ]

DISPATCH-1081 - Update doc for multicast delivery settlement


> Messages to multicast addresses are being released when no receivers attached
> -----------------------------------------------------------------------------
>
>                 Key: DISPATCH-1081
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1081
>             Project: Qpid Dispatch
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Alexander Rafferty
>            Assignee: Ganesh Murthy
>            Priority: Major
>
> When sending messages to a multicast address to which no consumers are 
> attached, the router sends back a disposition of RELEASED. The expected 
> behaviour is that all messages will be immediately settled by the ingress 
> router with a disposition of ACCEPTED as per section 2.4.1 of the Dispatch 
> router book:
> {quote}Multicast delivery is not reliable. If a producer sends an unsettled 
> delivery, the ingress router shall settle the delivery with ACCEPTED 
> disposition regardless of whether the message was delivered to any consumers.
> {quote}
> Is this a bug, or is this the expected behaviour? If this is the expected 
> behaviour, can the router be configured to always accept messages to 
> multicast addresses even where no consumers are actively listening?



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to