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

Ganesh Murthy commented on DISPATCH-1081:
-----------------------------------------

The problem is with the documentation in this case. Although multicast does not 
make any delivery guarantees, when no receivers are present for a multicasted 
address, releasing the the message actually gives the senderĀ  more information 
than simply accepting the message. If the message is released, the sender knows 
for sure that the message did not get anywhere. I will fix the documentation

> 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
>            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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to