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 GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/13 17:29:41 UTC
[jira] [Commented] (PROTON-1393) Memory leak with delayed
settlement
[ https://issues.apache.org/jira/browse/PROTON-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864025#comment-15864025 ]
ASF GitHub Bot commented on PROTON-1393:
----------------------------------------
GitHub user gemmellr opened a pull request:
https://github.com/apache/qpid-proton-j/pull/3
PROTON-1393: fully sever delivery refs during removal
Fully sever delivery references for related 'lists' during removal to prevent unexpected retention of old deliveries that arent otherwise reachable.
Updated version of #1 / #2.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gemmellr/qpid-proton-j delivery-lists
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-proton-j/pull/3.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3
----
----
> Memory leak with delayed settlement
> -----------------------------------
>
> Key: PROTON-1393
> URL: https://issues.apache.org/jira/browse/PROTON-1393
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.16.0, 0.17.0
> Reporter: Jonathan Kamke
>
> {{DeliveryImpl}} manages several doubly linked lists (of links, work and transportWork). However it does not function properly if removal is done out of order. It leaves object references in the next/previous pointers which on a large scale inhibit the system from garbage collecting these object, namely the {{DeliveryImpl}} object graph.
> In practice this was discovered when message consumers delay settlement of messages until after a period of time elapses (i.e. some async work is done in another thread). This causes out of order settlement to occur, leaving object references. Eventually the JVM will run out of memory and the process will crash. The heap can be examined to discover a large number of {{settled}} {{DeliveryImpl}}(s) which are holding references to themselves.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org