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

ASF GitHub Bot commented on ARTEMIS-1808:
-----------------------------------------

GitHub user franz1981 opened a pull request:

    https://github.com/apache/activemq-artemis/pull/2016

    ARTEMIS-1808 LargeServerMessageImpl leaks direct ByteBuffer

    largeMessagesFactory::newBuffer could create a pooled direct ByteBuffer
    that will not be released into the factory pool: using a heap ByteBuffer
    will perform more internal copies, but will make it simpler to be garbage
    collected.

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

    $ git pull https://github.com/franz1981/activemq-artemis ARTEMIS-1808

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

    https://github.com/apache/activemq-artemis/pull/2016.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 #2016
    
----
commit 44579986ef87c531a30d9d14e158333de4aec051
Author: Francesco Nigro <nigro.fra@...>
Date:   2018-04-15T15:31:05Z

    ARTEMIS-1808 LargeServerMessageImpl leaks direct ByteBuffer
    
    largeMessagesFactory::newBuffer could create a pooled direct ByteBuffer
    that will not be released into the factory pool: using a heap ByteBuffer
    will perform more internal copies, but will make it simpler to be garbage
    collected.

----


> LargeServerMessageImpl leaks direct ByteBuffer
> ----------------------------------------------
>
>                 Key: ARTEMIS-1808
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1808
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>            Priority: Major
>             Fix For: 2.5.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to