-
Bug
-
Resolution: Not a Bug
-
Optional
-
None
-
7.4.0.CD20-CR1
-
None
Tested scenario was cluster of two nodes using upstream DNS_PING. Request were send, everything was OK. Once cluster was scaled up from 2 -> 3. This stacktrace was emited into message log.
Note there was no failure of test requests were handled properly, just this unknown exception was thrown.
�[0m�[0m16:50:28,549 INFO [org.wildfly.clustering.ee.infinispan] (default task-3) WFLYCLEEINF0001: Failed to cancel JS9Z6O5m7xyJgONqxthYvmoZidhSmgek-AT_8G7e on primary owner.: java.util.concurrent.CancellationException at org.wildfly.clustering.server@7.4.0.CD20-redhat-00001//org.wildfly.clustering.server.dispatcher.ServiceRequest.receiveResponse(ServiceRequest.java:72) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.blocks.RequestCorrelator.handleResponse(RequestCorrelator.java:416) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.blocks.RequestCorrelator.dispatch(RequestCorrelator.java:364) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:308) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:582) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.JChannel.up(JChannel.java:784) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:913) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.FORK.up(FORK.java:138) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.FRAG3.up(FRAG3.java:165) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.FlowControl.up(FlowControl.java:351) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.pbcast.GMS.up(GMS.java:868) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:243) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1049) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.UNICAST3.addMessage(UNICAST3.java:772) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:753) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.UNICAST3.up(UNICAST3.java:405) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:592) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.Encrypt.handleEncryptedMessage(Encrypt.java:276) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.Encrypt.up(Encrypt.java:189) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:132) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.FailureDetection.up(FailureDetection.java:186) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:254) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.MERGE3.up(MERGE3.java:281) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.Discovery.up(Discovery.java:300) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.protocols.TP.passMessageUp(TP.java:1385) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.util.SubmitToThreadPool$SingleMessageHandler.run(SubmitToThreadPool.java:87) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at org.jboss.as.clustering.common@7.4.0.CD20-redhat-00001//org.jboss.as.clustering.context.ContextReferenceExecutor.execute(ContextReferenceExecutor.java:49) at org.jboss.as.clustering.common@7.4.0.CD20-redhat-00001//org.jboss.as.clustering.context.ContextualExecutor$1.run(ContextualExecutor.java:70) at java.base/java.lang.Thread.run(Thread.java:834)
Can you have a look if this something useful or just log noise and can be switch from INFO level to DEBUG level?
- is incorporated by
-
JBEAP-19839 EAP CD 20 OpenShift Image Release
- Closed
-
JBEAP-17060 OpenShift HA Tests Stabilisation Tracker
- Closed