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

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

Commit 48845b99848de3864bbe4246376237d5762b2de8 in qpid-dispatch's branch 
refs/heads/master from Gordon Sim
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=48845b9 ]

DISPATCH-1181: ensure local variable is initialised before it is used


> handling MAU when local address is not yet defined can result in wrong 
> treatment
> --------------------------------------------------------------------------------
>
>                 Key: DISPATCH-1181
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1181
>             Project: Qpid Dispatch
>          Issue Type: Bug
>            Reporter: Gordon Sim
>            Assignee: Gordon Sim
>            Priority: Major
>             Fix For: 1.5.0
>
>
> When dynamically configuring routers in a network, it is possible for an MAU 
> from one route rto reach another router for an address that the second router 
> has not yet had defined. At present this may cause the wrong treatment to be 
> applied to that address, which does not then get updated when the address 
> *is* defined. If the default distribution is unavailable then the MAU 
> handling exits without mapping the destination.
>  
> E.g.
>  
> start router 1
> define a multicast address on it
> create receiver on that address & router
> start router 2
> wait a bit before creating the same multicast address
> create receiver on this router using the same address
> send to the address on router 2
>  
> The address is treated as anycast (the default distribution). Using qdstat -a 
> the incorrect (or undesired) distribution can also be seen.



--
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