]
Richard Janík updated WFLY-6356:
--------------------------------
Affects Version/s: (was: 12.0.0.Beta1)
Error while processing a prepare in a single-phase transaction due to
replication timeout
-----------------------------------------------------------------------------------------
Key: WFLY-6356
URL:
https://issues.jboss.org/browse/WFLY-6356
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.0.0.Final
Reporter: Michal Vinkler
Assignee: Paul Ferraro
This is a separate issue originally logged as part of JBEAP-794 (#4 in this
[
comment|https://issues.jboss.org/browse/JBEAP-794?focusedCommentId=131706...]).
Seen in ejb-remote, ejb-ejbservlet and http-session scenarios with *REPL* cache and
*SYNC* replication.
TimeoutException occured after perf18 (or any other node) rejoined a cluster (after
graceful shutdown, jvmkill or undeploy - it doesn't matter), but it does not seem to
affect client:
{code}
[JBossINF] [0m[31m03:23:38,458 ERROR
[org.infinispan.transaction.impl.TransactionCoordinator] (default task-24) ISPN000097:
Error while processing a prepare in a single-phase transaction:
org.infinispan.util.concurrent.TimeoutException: Replication timeout for perf19
[JBossINF] at
org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:765)
[JBossINF] at
org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$175(JGroupsTransport.java:612)
[JBossINF] at
java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602)
[JBossINF] at
java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
[JBossINF] at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
[JBossINF] at
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962)
[JBossINF] at
org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47)
[JBossINF] at
org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16)
[JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[JBossINF] at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
[JBossINF] at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[JBossINF] at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[JBossINF] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[JBossINF] at java.lang.Thread.run(Thread.java:745)
{code}
Also, JBEAP-3779 an JBEAP-3781 (and partially also JBEAP-3782) accompany this issue, see
[occurrences
report|http://download.eng.brq.redhat.com/scratch/mvinkler/reports/occurr...]
Server link:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...