[
https://issues.apache.org/jira/browse/QPIDJMS-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPIDJMS-342:
-----------------------------------
Description:
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.connectTimeout value
was:
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
> 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
> Priority: Major
> 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.connectTimeout value
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
