You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ted Ross (JIRA)" <ji...@apache.org> on 2016/11/03 12:45:58 UTC
[jira] [Updated] (DISPATCH-535) Use correct lifecycle management
for Proton objects
[ https://issues.apache.org/jira/browse/DISPATCH-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross updated DISPATCH-535:
------------------------------
Summary: Use correct lifecycle management for Proton objects (was: Dispatch memory increases on long lived link routed connections )
> Use correct lifecycle management for Proton objects
> ---------------------------------------------------
>
> Key: DISPATCH-535
> URL: https://issues.apache.org/jira/browse/DISPATCH-535
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
> Affects Versions: 0.7.0
> Reporter: Ganesh Murthy
> Assignee: Ganesh Murthy
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments: qdrouterd1.conf, repro.py
>
>
> To reproduce this issue, set up a link route to a broker and set up a client that continually tries to create a receivers for non-existent queues on the broker
> Please see attached reproducer client program and router config.
> The problem seems to be that the proton library used by dispatch does not free links and sessions associated with open connections and so the memory keeps slowly building up. The links and sessions are freed when the connection is terminated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org