[
https://issues.apache.org/jira/browse/PROTON-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838322#comment-15838322
]
ASF GitHub Bot commented on PROTON-1393:
----------------------------------------
GitHub user jkamke opened a pull request:
https://github.com/apache/qpid-proton-j/pull/2
Delivery link leak
Supersedes apache/qpid-proton-j/pull/1 for
https://issues.apache.org/jira/browse/PROTON-1393
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jkamke/qpid-proton-j delivery-link-leak
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-proton-j/pull/2.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 #2
----
commit 3c315a31548aa8ce2570b61eda3cfecf783b4f72
Author: Robert Gemmell <[email protected]>
Date: 2016-12-08T15:37:59Z
PROTON-1374: update versions for 0.16.0 (RC1)
commit b942d5636479b3ba51a842ee2734171e5722a9bd
Author: Robert Gemmell <[email protected]>
Date: 2016-12-08T17:33:40Z
PROTON-1374: bump versions to 0.16.1-SNAPSHOT
commit 059322cb19c77514f58c62fa7dbd580faf70cf7a
Author: JK <[email protected]>
Date: 2017-01-19T17:15:08Z
fix memory leak by cleaning up references and removing links safely
commit 45009610ef8af0d558cd0a1adf1797525db2522c
Author: JK <[email protected]>
Date: 2017-01-20T02:31:12Z
test for memory leak
commit 41151a52dbd30cfe0d5471fb7bfe1502305578a4
Author: JK <[email protected]>
Date: 2017-01-20T02:32:48Z
attribution for verifier
commit 541d1974cc938ac64ffb9583ab8351dcd8072fab
Author: JK <[email protected]>
Date: 2017-01-25T18:22:41Z
Fixes #1 and addresses https://issues.apache.org/jira/browse/PROTON-1393
against master
----
> 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
> 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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
