Skip to content

ARTEMIS-1776] - Implement asynchronous flow control on bridge and clustered bridge#247

Open
JiriOndrusek wants to merge 3 commits into
rh-messaging:jboss-1.5.5-xfrom
JiriOndrusek:Asynchronous_flow_control_on_the_bridge_155x
Open

ARTEMIS-1776] - Implement asynchronous flow control on bridge and clustered bridge#247
JiriOndrusek wants to merge 3 commits into
rh-messaging:jboss-1.5.5-xfrom
JiriOndrusek:Asynchronous_flow_control_on_the_bridge_155x

Conversation

@JiriOndrusek

Copy link
Copy Markdown

Issue: https://issues.apache.org/jira/browse/ARTEMIS-1776

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.

These changes avoids that possibility.

howardgao and others added 3 commits April 11, 2018 08:34
…n bridges

The cluster connection bridge hard codes its producerWindowSize to -1
(meaning no producer flow control) even if you configure it otherwise.

Cherry-picked from 1e6e1f7
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 3c54609
@JBossJenkins

Copy link
Copy Markdown

Can one of the admins verify this patch?

spyrkob pushed a commit to spyrkob/jboss-activemq-artemis that referenced this pull request Apr 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants