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

ASF GitHub Bot commented on PROTON-1393:
----------------------------------------

GitHub user jkamke opened a pull request:

    https://github.com/apache/qpid-proton-j/pull/1

    Memory leak with delayed settlement

    addresses https://issues.apache.org/jira/browse/PROTON-1393
    
    Change should be portable to 0.17.0

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jkamke/qpid-proton-j delivery-memory-leak

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-proton-j/pull/1.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 #1
    
----
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

----


> 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
>
> If message consumers delay settlement of messages until after a period of 
> time elapses (i.e. some work is done), then the number of {{DeliveryImpl}}(s) 
> in the heap will rise. Eventually the JVM will run out of memory and the 
> process will crash.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to