You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2017/10/17 18:44:00 UTC

[jira] [Created] (QPIDJMS-342) Missed connect error on start can lead to hung failover reconnect cycle

Timothy Bish created QPIDJMS-342:
------------------------------------

             Summary: Missed connect error on start can lead to hung failover reconnect cycle
                 Key: QPIDJMS-342
                 URL: https://issues.apache.org/jira/browse/QPIDJMS-342
             Project: Qpid JMS
          Issue Type: Bug
          Components: qpid-jms-client
    Affects Versions: 0.26.0
            Reporter: Timothy Bish
            Assignee: Timothy Bish
             Fix For: 0.27.0


In some cases where the jms.connectTimeout is tripped during socket level connection and the failover transport bits are in use the client an fall into a reconnect loop or stall waiting for an error callback that won't be triggered.  

One workaround exists which is to configure the transport level socket connect timeout to be lower than the jms.connectionTimeout value



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org