[jira] [Resolved] (QPID-6788) NetworkConnection can occupy large amounts of direct memory causing the broker to go OutOfMemory

["Keith Wall (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/QPID-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall resolved QPID-6788.
------------------------------
    Resolution: Fixed

I paired with Alex on the latter (web socket) part of this task.

> NetworkConnection can occupy large amounts of direct memory causing the broker to go OutOfMemory
> ------------------------------------------------------------------------------------------------
>
>                 Key: QPID-6788
>                 URL: https://issues.apache.org/jira/browse/QPID-6788
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: qpid-java-6.0
>            Reporter: Lorenz Quack
>            Assignee: Lorenz Quack
>         Attachments: 0001-QPID-6788-Java-Broker-Limit-the-amount-of-memory-tha.patch, 0001-QPID-6788-Java-Broker-Limit-the-amount-of-memory-tha.patch
>
>
> Messages get passed to {{NonBlockingConnection}} in the {{send()}} method which holds them in the private {{_buffers}} field. The {{doWrite()}} method consumes the messages and disposes them from the IOThread. However, there is no limit on how many messages/buffer can be in the {{_buffers}} variable.
> In one test there were about 2000 {{QpidByteBuffers}} in {{_buffers}} accounting for approximately 500 MBytes direct memory.
> This happens can cause the Broker to go OutOfMemory especially when the client is useing prefetch.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org