activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolay Martynov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-4971) OOM in DemandForwardingBridge
Date Thu, 16 Jan 2014 10:51:20 GMT

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

Nikolay Martynov updated AMQ-4971:
----------------------------------

    Attachment: AMQ-4971.patch

Attached patch with workaround for those who face OOM in network bridge. This is hardly a
solution (might be lower vm performance on small messages, might be less delivery guarantees
over bridges) but at least it allows JVM not to crash with OOM.

> OOM in DemandForwardingBridge
> -----------------------------
>
>                 Key: AMQ-4971
>                 URL: https://issues.apache.org/jira/browse/AMQ-4971
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.9.0
>            Reporter: Yuriy Sidelnikov
>              Labels: features
>         Attachments: AMQ-4971.patch
>
>
> DemandForwardingBridge sends messages to the other broker and asynchronously waits for
ACKs keeping message bodies in heap. Amount of un-ACK-ed messages kept in heap is not limited.
If local producer is fast then whole heap will be consumed by messages waiting to be ACK-ed
by other broker.
> Possible option to fix the issue:
> Don't wait for ACK from other broker when forwarding the message if some threshold of
un-ACK-ed messages is reached.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message