You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2017/06/20 16:23:00 UTC
[jira] [Commented] (QPID-7367) [JCA] QpidRASessionImpl#closeSession
does not destroy the underlying connection
[ https://issues.apache.org/jira/browse/QPID-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056034#comment-16056034 ]
Keith Wall commented on QPID-7367:
----------------------------------
Won't fix. Feature removed by QPID-7716.
> [JCA] QpidRASessionImpl#closeSession does not destroy the underlying connection
> -------------------------------------------------------------------------------
>
> Key: QPID-7367
> URL: https://issues.apache.org/jira/browse/QPID-7367
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Keith Wall
> Priority: Minor
>
> I notice that {{QpidRASessionImpl#closeSession()}} stops the managed connections, closes consumers and producers but fails to destroy the managed connection. This means that the underlying connection to the Broker remains open.
> I think org.apache.qpid.ra {{QpidRASessionImpl#closeSession}} simply needs to call mc.destroy() before nulling the reference.
> I discovered this because the system test suite leaves behind threads belonging to the {{AMQConnection#_taskPool}}. These are the connections used by the JCA system test suite.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org