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-1776) Implement asynchronous flow control on bridge and clustered bridge
Date Tue, 17 Apr 2018 14:59:00 GMT

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

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

Commit 3c546092788c1d6cf7f16d5a2b0938de00f2410a in activemq-artemis's branch refs/heads/1.x
from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=3c54609 ]

ARTEMIS-1776 Blocked Bridge is not resuming after reconnect

This is still part of ARTEMIS-1776 fix, which still part of the same release as we are on
now.
Hence I'm not opening a new JIRA for this one.

Cherry-picked from e5bce13316f7e81bb15a12592622df2ea2632a35


> Implement asynchronous flow control on bridge and clustered bridge
> ------------------------------------------------------------------
>
>                 Key: ARTEMIS-1776
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1776
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 2.5.0
>            Reporter: clebert suconic
>            Assignee: clebert suconic
>            Priority: Major
>             Fix For: 2.5.1
>
>
> Currently the flow control on the Bridge is based on back pressure only, through Netty
writeable interfaces.
>  
> If the user selected a positive producerWindowSize the Queue may block while the Processing
is happening. What could lead to distributed deadlocks on the Bridge.
>  
> This will avoid that possibility.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message