[
https://issues.apache.org/jira/browse/QPIDJMS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707152#comment-14707152
]
ASF subversion and git services commented on QPIDJMS-94:
--------------------------------------------------------
Commit fe93f01037825228deeda3f5ddfce001314f8c1f in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=fe93f01 ]
QPIDJMS-94: mark begin of connection close and use to prevent new connection
attempts after that point
> the failover provider can erroneously reconnect following Connection close.
> ---------------------------------------------------------------------------
>
> Key: QPIDJMS-94
> URL: https://issues.apache.org/jira/browse/QPIDJMS-94
> 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 the JMS Connection object is closed while using the failover provider,
> the underlying AMQP connection is 'destroyed' by the AmqpProvider instance,
> then the FailoverProvider itself is marked closed. During the process, there
> is a race where and the transport may report to its listeners that it has
> closed, and cause the FailoverProvider to re-establish an AMQP connection.
> This is then left behind without being closed, keeping the JVM running due to
> use of a non-daemon thread.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
