[infinispan-issues] [JBoss JIRA] Commented: (ISPN-920) TimeoutException: Replication timeout in DIST_ASYNC mode

TimeoutException: Replication timeout in DIST_ASYNC mode -------------------------------------------------------- Key: ISPN-920 URL: https://issues.jboss.org/browse/ISPN-920 Project: Infinispan Issue Type: Bug Affects Versions: 4.2.0.Final Reporter: Dror Bereznitsky Assignee: Manik Surtani Fix For: 4.2.1.CR2, 4.2.1.Final Attachments: infinispan-test.xml, InfinispanClusterTest.java, jgroups-test.xml, unit-test-1.log, unit-test-2.log I'm running a simple unit test for checking our Infinispan setup. The test involves starting two instances of Infinispan with a single cache in DIST_ASYNC mode. The test creates the cache and start putting new values every X ms. After starting the 2nd or 3rd test instance I'm always getting the following exception: {code} org.infinispan.util.concurrent.TimeoutException: Replication timeout for DRORB-LAP-TAN-26976 at org.infinispan.remoting.transport.AbstractTransport.parseResponseAndAddToResponseList(AbstractTransport.java:49) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:414) at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:101) at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:125) at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:230) at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:217) at org.infinispan.remoting.rpc.RpcManagerImpl.broadcastRpcCommand(RpcManagerImpl.java:200) at org.infinispan.distribution.JoinTask.performRehash(JoinTask.java:132) at org.infinispan.distribution.RehashTask.call(RehashTask.java:53) at org.infinispan.distribution.RehashTask.call(RehashTask.java:33) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) {code} Disabling the L1 cache resolves the problem. Attached are the configuration files, test console output and the test source code.