[
https://issues.apache.org/jira/browse/QPID-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall resolved QPID-4301.
------------------------------
Resolution: Won't Fix
Agreed in a product backlog review - won’t fix.
> Remediate the failover functionality
> ------------------------------------
>
> Key: QPID-4301
> URL: https://issues.apache.org/jira/browse/QPID-4301
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.16, 0.18, 0.19
> Reporter: Alex Rudyy
>
> The existing failover functionality is not fully transparent for the client
> application.
> On running the failover the client might ran into the following issue:
> * Previous IOReceiver thread can start a failover again when failover
> thread just re-established the connection
> * Connection closed flag is reset on every connection attempt. There is a
> chance when user calls connection#close and failover is in progress the
> connection closed flag will be reset and failover will restore-the connection
> * JMSException can be thrown on Session#close, MessageCondumer#close(),
> MessageProduce#send if they are called when connectivity is lost but failover
> thread has not started yet.
> * Whilst connecting to the node when tcp connection is established and
> amqp connection is in process of establishing the network outages can result
> in the network connection being closed but connection state waiters are not
> get notified. As result waiters will wait until timeout (30 seconds ) expires
> before trying next re-connection attempt.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
