[ 
https://issues.apache.org/jira/browse/DISPATCH-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Charles E. Rolke resolved DISPATCH-1709.
----------------------------------------
    Fix Version/s: 1.13.0
       Resolution: Fixed

Fixed at Commit 58c8ff7

> Fallback destination rcvr on edge router is unaware that primary rcvr exited
> ----------------------------------------------------------------------------
>
>                 Key: DISPATCH-1709
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1709
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Router Node
>    Affects Versions: 1.12.0
>         Environment: This can be reproduced by applying
> [https://github.com/apache/qpid-dispatch/pull/775] at commit 204580a
>  
>            Reporter: Charles E. Rolke
>            Priority: Major
>             Fix For: 1.13.0
>
>         Attachments: ctest-console-5448b.txt, fd-20200714-5448b.svg
>
>
> Fixing issue DISPATCH-1708 reveals another problem.
> Test_28 fails with
> {code:java}
> 63: ======================================================================
> 63: FAIL: test_28_switchover_local_edge_alt_remote_edge 
> (system_tests_fallback_dest.RouterTest)
> 63: ----------------------------------------------------------------------
> 63: Traceback (most recent call last):
> 63:   File 
> "/home/chug/git/qpid-dispatch/tests/system_tests_fallback_dest.py", line 297, 
> in test_28_switchover_local_edge_alt_remote_edge
> 63:     self.assertEqual(None, test.error)
> 63: AssertionError: None != 'Timeout Expired - n_tx=256, n_rx=0, 
> n_rel=111117, phase=1, local_rel=1246'
> {code}
> Apparently the fallback dest receiver router EA1 is never notified that the 
> primary receiver on router EB1 has exited.  EA1 then keeps sending messages 
> for the test to INT.A where they are released.



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