Description of problem:
Since this commit:
... Infinispan is no longer usable in WildFly 9, whose transports are configured to use ForkChannel rather than JChannels. The underlying issue is described in JGRP-1905. The commit above adds a cluster-wide RPC on view change (from org.infinispan.topology.ClusterTopologyManagerImpl.confirmMembersAvailable(), the message for which inevitably arrives on the newly starting node before the requisite fork channel is registered. The RPC eventually times out since Infinispan's RPC dispatcher will wait for a response that will never come.
*** This bug has been marked as a duplicate of bug 1189138 ***