You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Lorenz Quack (JIRA)" <ji...@apache.org> on 2016/10/24 14:31:00 UTC
[jira] [Updated] (QPID-7465) [Java Broker] Stop ServerEncoder on
AMQP 0-10 from unnecessarily allocating ByteBuffers
[ https://issues.apache.org/jira/browse/QPID-7465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lorenz Quack updated QPID-7465:
-------------------------------
Summary: [Java Broker] Stop ServerEncoder on AMQP 0-10 from unnecessarily allocating ByteBuffers (was: [Java Broker] Stop ServerEncoder from unnecessarily allocating ByteBuffers)
> [Java Broker] Stop ServerEncoder on AMQP 0-10 from unnecessarily allocating ByteBuffers
> ---------------------------------------------------------------------------------------
>
> Key: QPID-7465
> URL: https://issues.apache.org/jira/browse/QPID-7465
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Lorenz Quack
> Assignee: Alex Rudyy
> Fix For: qpid-java-6.0.5, qpid-java-6.1
>
> Attachments: QPID-7465.diff, QPID-7465_v2.diff, QPID-7465_v2.diff
>
>
> As reported by [this email thread|http://qpid.2158936.n2.nabble.com/java-broker-6-0-2-OOM-tp7651831.html] the broker can currently run out of direct memory without flow-to-disk ever kicking in.
> A defect in {{SeverEncoder#init()}} means that we allocate a new 8 kB direct bytebuffer everytime it is called (i.e. on every AMQP 0-10 method or command). This is wasteful and in some cases the GC does not collect these direct byte buffers fast enough leading to the OOM.
--
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