You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/06 14:04:00 UTC
[jira] [Commented] (ARTEMIS-1776) Implement asynchronous flow
control on bridge and clustered bridge
[ https://issues.apache.org/jira/browse/ARTEMIS-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428362#comment-16428362 ]
ASF GitHub Bot commented on ARTEMIS-1776:
-----------------------------------------
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/1996
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis bridge
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1996.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1996
----
commit 91ed6e3a726b58d04d4155543f1701c6ee0d0ba2
Author: Clebert Suconic <cl...@...>
Date: 2018-04-06T14:00:43Z
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.
----
> 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)