[jboss-jira] [JBoss JIRA] (JGRP-1905) FORK: RPCs might block if fork channel or fork stack is not available

[Paul Ferraro (JIRA)]

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

Paul Ferraro commented on JGRP-1905:
------------------------------------

Your strategy of connecting all fork channels first doesn't gel with the way WildFly provisions its channels.  Infinispan is no longer the only consumer of JGroups channels, as was the case in AS7 - and thus no longer designed to control the lifecycle of the main channel.  Effectively, there is no definitive set of forks for a given deployment - these are created and connected as needed by the requisite clustering services required to fulfill the components used by that deployment.

> FORK: RPCs might block if fork channel or fork stack is not available
> ---------------------------------------------------------------------
>
>                 Key: JGRP-1905
>                 URL: https://issues.jboss.org/browse/JGRP-1905
>             Project: JGroups
>          Issue Type: Bug
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>            Priority: Critical
>             Fix For: 3.6.2
>
>
> When we have nodes A,B,C,D, but fork-stack "fs-2" is not available on B, or fork-channel "ch-3" is not available on B, then an RPC invoked by A on all cluster nodes will time out.
> h5. Solution
> * Throw an exception on B if a fork-stack or -channel is not available on a target node. This way, the RPC would return quickly and B's response would be set to the exception (e.g. "fork channel fc-2 not available").



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)