activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-350) possible OOM in replication manager
Date Tue, 23 Feb 2016 19:18:18 GMT

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

ASF subversion and git services commented on ARTEMIS-350:
---------------------------------------------------------

Commit 2fcd474bb3ea83c696e2794cd7b5951494a2b20a in activemq-artemis's branch refs/heads/master
from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=2fcd474 ]

ARTEMIS-350 fix for potential race

It's possible for the latch used for flow control here to get out of sync. In
other words, multiple count-downs can occur between count-ups so that the latch
always has a count > 0. When this situation arises then every single packet
sent to the replica is delayed by 5 seconds.

The solution here essentially is to eliminate the latch completely and use a
condition/wait/notify pattern.


> possible OOM in replication manager
> -----------------------------------
>
>                 Key: ARTEMIS-350
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-350
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Andy Taylor
>            Assignee: Andy Taylor
>             Fix For: 1.3.0
>
>
> This is becausee we have no flow control, we need to throttle back when the channel is
not writable



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

Mime
View raw message