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

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

GitHub user franz1981 opened a pull request:

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

    ARTEMIS-1025 OutOfDirectMemoryError raised from Netty

    It solve the OOM issue while under heavy load while:
    - allowing the NettyConnection to perform a (configurable) weak form of 
backpressure on unbatched "big" messages
    - allowing multiple (concurrent) clients to query the memory usage of the 
connection
    - allowing batching without involving further copies of the data
    - providing detailed memory load informations on OOM errors

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

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

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

    https://github.com/apache/activemq-artemis/pull/1119.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 #1119
    
----
commit a421cd5b19e95feddfbb4b35e423591617e86283
Author: Francesco Nigro <nigro....@gmail.com>
Date:   2017-03-15T13:52:52Z

    ARTEMIS-1025 OutOfDirectMemoryError raised from Netty

----


> OutOfDirectMemoryError raised from Netty
> ----------------------------------------
>
>                 Key: ARTEMIS-1025
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1025
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>
> If you send and receive a lot of messages in short time to Artemis via Netty 
> connector, the OutOfDirectMemoryError exception is thrown from the client.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to