[ https://issues.jboss.org/browse/JGRP-1871?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on JGRP-1871: ------------------------------------ "What's the time between creating the channel and calling connect() on it ?" I mean new JChannel(...) vs channel.connect(...). In WildFly I have one service that creates and closes a channel, and a child service that connects and disconnects a channel. This way a single channel instance can be connected, disconnected, and reconnected without having to destroy and recreate it. These 2 services are started by different threads and are completely managed by WildFly's service container. Given the right architecture, I'm sure that this could be reproduced fairly easily. Traditionally, both Infinispan and JBoss AS will create and connect a channel in the same thread. The separation of the two is unique to WF8. My workaround, which so far seems to work, is here: https://github.com/pferraro/wildfly/commit/99d18fffcae310dfc69c6d6abfe01f... I'm relying on WF's ServiceContainer itself to perform synchronization of the thread memory spaces. I haven't seen this issue in our CI jobs since this fix went into place. -- This message was sent by Atlassian JIRA (v6.2.6#6264)