Jiri Daněk commented on QPIDJMS-342:

correct name of the parameter mentioned in workaround is {{jms.connectTimeout}}

> 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.connectionTimeout value

This message was sent by Atlassian JIRA

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

Reply via email to