[jboss-jira] [JBoss JIRA] (JGRP-2301) UFC: add back to configs even if TCP is transport

[Bela Ban (Jira)]

    [ https://issues.jboss.org/browse/JGRP-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657261#comment-13657261 ] 

Bela Ban commented on JGRP-2301:
--------------------------------

This was observed in an actual customer case where cross-site replication done *asynchronously* led to OOMEs on the receivers.

> UFC: add back to configs even if TCP is transport
> -------------------------------------------------
>
>                 Key: JGRP-2301
>                 URL: https://issues.jboss.org/browse/JGRP-2301
>             Project: JGroups
>          Issue Type: Enhancement
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 4.0.16
>
>
> Currently, none of the TCP-based stacks have UFC in them. This is bad, as async messages can overwhelm the receiver. Point in case is cross-site replication: the bridge using TCP replicates updates to the other site masters quickly, but the updates are only passed to the thread pool for processing, exhausting memory over time.
> Although TCP does perform flow control, the application code at the receiver may delay delivery and thus the sender would block if UFC was present.
> However, the absence of UFC leads to thread pool (and queue) overflow at the receiver(s) if messages are constantly sent at a rate greater that when the receiver(s) can process.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)