1 Reply Latest reply on May 2, 2016 1:45 PM by Pedro Ruivo

    org.infinispan.util.concurrent.TimeoutException: Replication timeout

    tomas11 Novice

      Hi all


      Here and then with Infinispan 8 we get in logs following error


      org.infinispan.util.concurrent.TimeoutException: Replication timeout for a4b9ddda-ef85-4810-91b6-57f12107fe78-32868

               at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:801)

               at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$83(JGroupsTransport.java:633)

               at java.util.concurrent.CompletableFuture.uniApply(Unknown Source)

               at java.util.concurrent.CompletableFuture$UniApply.tryFire(Unknown Source)

               at java.util.concurrent.CompletableFuture.postComplete(Unknown Source)

               at java.util.concurrent.CompletableFuture.complete(Unknown Source)

               at org.infinispan.remoting.transport.jgroups.SingleResponseFuture.call(SingleResponseFuture.java:46)

               at org.infinispan.remoting.transport.jgroups.SingleResponseFuture.call(SingleResponseFuture.java:17)

               at java.util.concurrent.FutureTask.run(Unknown Source)

               at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

               at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

               at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

               at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

               at java.lang.Thread.run(Unknown Source)


      We are using both replication and distribution caches in ASYNC mode.


      Can be for this any specific reason? Or is here general help to increase timeout?


      What property needs to be set to rise this timeout? In latest configuration for infinispan 8 I have not found something like "replTimeout".




        • 1. Re: org.infinispan.util.concurrent.TimeoutException: Replication timeout
          Pedro Ruivo Apprentice

          Hi Tomas,


          It is not easy to find the causes for a replication timeout. If it doesn't happen frequently, I would say some network contention, GC pause or some write intensive/high contention case. If you have logging enable, you can attach the logs and I'll give take a look to see if something strange is happening.


          To increase the replication timeout, you need to set the attribute 'remote-timeout' when define your cache. For example:


          <replicated-cache ... remote-timeout="20000">

          <distributed-cache ... remote-timeout="20000">

          The values are in milliseconds and the default is 15 seconds (it is enough for most uses cases).