[
https://issues.apache.org/jira/browse/QPIDJMS-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707153#comment-14707153
]
ASF subversion and git services commented on QPIDJMS-95:
--------------------------------------------------------
Commit e46354bd724f10a6e670ebd821987b99cbf2e943 in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=e46354b ]
QPIDJMS-95: add some extra trace logging, make exception message slightly
clearer
> the failover provider can block if the transport drops while establishing the
> new connection.
> ---------------------------------------------------------------------------------------------
>
> Key: QPIDJMS-95
> URL: https://issues.apache.org/jira/browse/QPIDJMS-95
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.4.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.5.0
>
>
> When restablishing a connection after it drops, if the new connections
> transport drops during the process of opening the connection the failover
> provider can block awaiting its completion which will never come. This was
> observed agaisnt an instance of qpidd being stopped and started every few
> seconds. Its not clear why the transport dropped immediately after being
> created, but it should be handled, and the incopminete connection open
> aborted so another further attempts can take place.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
