[ https://issues.apache.org/jira/browse/QPIDJMS-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208144#comment-16208144 ]
ASF subversion and git services commented on QPIDJMS-342: --------------------------------------------------------- Commit 95070f162e2b85b7f598c660b16bc77934638aa9 in qpid-jms's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=95070f1 ] QPIDJMS-342 Ensure that the global connect timeout gets honored Better handle the jms.connectTimeout having been reached so that the connection error triggers in a timely manner and the failover transport gets notified correctly. > 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org