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

ASF GitHub Bot commented on DISPATCH-1693:
------------------------------------------

ChugR opened a new pull request #765:
URL: https://github.com/apache/qpid-dispatch/pull/765


   QDRC_EVENT_ADDR_ONE_SOURCE event on fallback link provokes a link
   closure.
   This commit fixes an issue exposed by DISPATCH-1684 
(https://github.com/apache/qpid-dispatch/pull/756)
   The test suite passes with this fix but are there other cases where closing 
the fallback link is desirable?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


> Edge router closes fallback receiver link when local primary receiver closes
> ----------------------------------------------------------------------------
>
>                 Key: DISPATCH-1693
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1693
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Router Node
>    Affects Versions: 1.12.0
>            Reporter: Charles E. Rolke
>            Priority: Major
>
> This bug is exposed by the fix to tests/system_tests_fallback_dest.py. See 
> https://issues.apache.org/jira/browse/DISPATCH-1684
> The design goal configuration for test_29 is:
>  * sender EA1
>  * primary receiver EA1
>  * fallback receiver INT.A
> The fix for this issue must be committed before the fix for DISPATCH-1684. 
> Otherwise the change to the test will introduce a hard error and a guaranteed 
> self test failure.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to