[
https://issues.apache.org/jira/browse/DISPATCH-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943791#comment-16943791
]
Ken Giusti commented on DISPATCH-1423:
--------------------------------------
Good catch - yes this is a new bug introduced on 1.9.0 by
[DISPATCH-1266|https://issues.apache.org/jira/browse/DISPATCH-1266]
Before that patch multicast messages were treated as "topic-like" - the sender
could send multicast messages whether or not a subscriber exists (much like the
way a broker topic works).
See [DISPATCH-779|https://issues.apache.org/jira/browse/DISPATCH-779] for the
relevant behavior.
So the correct behavior should be that the sender sends all 500 w/o blocking.
However if the messages are sent unsettled the client will get a RELEASED
outcome if no consumer present (pre 1.9.0 the outcome would have been ACCEPTED).
> Multicast sender with no receiver has first 250 messages released
> -----------------------------------------------------------------
>
> Key: DISPATCH-1423
> URL: https://issues.apache.org/jira/browse/DISPATCH-1423
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
> Affects Versions: 1.8.0
> Reporter: Charles E. Rolke
> Assignee: Ken Giusti
> Priority: Major
> Attachments: INTB-250-released-1.8.0.html, INTB.conf
>
>
> When a sender starts and there's no receiver already attached then the first
> 250 messages the sender sends get released. After that the router waits for
> the a receiver to attach before issuing more credit to the sender. The proton
> c++ simple_send and simple receive clients expose this problem.
> 1. Start router with attached config file
> 2. Start sender
> simple_send -a 127.0.0.1:5672/multicast/q1 -m 500
> 3. Start receiver
> simple_recv -a 127.0.0.1:5672/multicast/q1 -m 500
> The sender competes with 'all messages confirmed'.
> The receiver is waiting for the second 250 messages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
