[
https://issues.apache.org/jira/browse/QPID-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-3210.
------------------------------
Resolution: Incomplete
Fix Version/s: 0.20
This has been done for the 1.0 implementation (if the entire graph rooted in a
connection is not longer referenced, it will close and cleanup).
However the 0-10 implementation has not and will not be changed.
> Connection destructor should close the connection
> -------------------------------------------------
>
> Key: QPID-3210
> URL: https://issues.apache.org/jira/browse/QPID-3210
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Reporter: Jerome Ajot
> Assignee: Gordon Sim
> Labels: RAII, close, connection, destructor
> Fix For: 0.20
>
>
> Description of problem:
> When a qpid::messaging::Connection goes out-of-scope, it should close itself.
> As no data are reachable, it can generate leaks and resource locks if it
> stays open.
> Version-Release number of selected component (if applicable):
> All
> How reproducible:
> Easy
> Steps to Reproduce:
> 1. Create a Connection and Session.
> 2. Create a Receiver which creates a exclusive queue.
> 3. Let the connection goes out-of-scope.
>
> Actual results:
> The connection is not closed and the queue unreachable.
> Expected results:
> When a connection goes out-of-scope and cannot be recovered, there is no
> reason to keep it open and hold the resources (such as Sessions, Senders, and
> Receivers) attached to it. It should close the Sessions, Receivers, and
> Senders, and invoke the Sessions, Receivers, and Senders destructors, then
> close itself.
> It should cleanup all data that cannot be reachable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
