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

ASF subversion and git services commented on QPIDJMS-344:
---------------------------------------------------------

Commit b8bdec81b13e52e0f924ad01847a54d49e7106fa in qpid-jms's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=b8bdec8 ]

QPIDJMS-344 Update the discovered URIs for the remote on connect

During failover reconnection process the discovered remote hosts from
the open before signaling that the connection is restored to ensure that
the failover transport state matches expectations.


> FailoverWithAmqpOpenProvidedServerListIntegrationTest sporadic test failures 
> in CI
> ----------------------------------------------------------------------------------
>
>                 Key: QPIDJMS-344
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-344
>             Project: Qpid JMS
>          Issue Type: Improvement
>    Affects Versions: 0.26.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 0.27.0
>
>
> During CI testing the failover integration tests that are checking that 
> updated failover URIs provided from remote peers are handled correctly have 
> been sporadically failing.  This is due to the way the updates are handled 
> from the remote leading to an event that can fire in an unexpected ordering 
> relative to the connection established / connection recovered events.  
> Because of the mixed ordering of events the integration tests can check the 
> updated URIs at the wrong time and not see the URI updates they are 
> expecting.  
> Refactoring the handling of the updated failover URs should be done to make 
> the ordering of how these are all handled consistent.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to