You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/01/05 21:25:58 UTC

[jira] [Commented] (DISPATCH-603) address resource leak

    [ https://issues.apache.org/jira/browse/DISPATCH-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802567#comment-15802567 ] 

ASF subversion and git services commented on DISPATCH-603:
----------------------------------------------------------

Commit 4e3843dc3b2320382e7ede869391ae51070f85ca in qpid-dispatch's branch refs/heads/master from [~tross@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=4e3843d ]

DISPATCH-603 - Fixed bug where addresses can go unreclaimed if the last activity is the removal of tracked deliveries.  Hat tip to Ganesh Murthy who identified the cause of this bug.
This also fixes a bug where core address structures were accessed from an I/O thread.


> address resource leak
> ---------------------
>
>                 Key: DISPATCH-603
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-603
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Routing Engine
>    Affects Versions: 0.7.0
>         Environment: Centos 7, JDK 8
>            Reporter: Rohan Mars
>            Assignee: Ganesh Murthy
>             Fix For: 0.8.0
>
>         Attachments: test-app-address-leak.tar
>
>
> A multi-node router mesh will leak addresses, causing a memory increase.
> The test case attached can reproduce the problem.
> The addresses that are leaked are temporary reply addresses.
> See the README for instructions on how to run.



--
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