[
https://issues.apache.org/jira/browse/QPID-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978594#comment-14978594
]
ASF subversion and git services commented on QPID-6788:
-------------------------------------------------------
Commit 1711035 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1711035 ]
QPID-6788: [Java Broker] NonBlockingConnections now only read and process work
after all buffered data has been written to the network.
> NonBlockingConnection 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
