TcpConnection.Receiver#run should use logger to handle exception rather than rely on UncaughtExceptionHandler ------------------------------------------------------------------------------------------------------------- Key: JGRP-2489 URL: https://issues.redhat.com/browse/JGRP-2489 Project: JGroups Issue Type: Bug Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Major Testing scenario: Create cluster of 3 nodes using upstream kube ping protocol. With multiple clients make http requests against such cluster for a while. We did not notice functional failure of test. Part of test is checking for unknown error messages in log so that is why we noticed. Can you have a look if it is useful to have this error message in logs? {code} 15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) Exception in thread "Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4" java.lang.RuntimeException: failed handling message from 10.131.0.184:7600: java.io.IOException: Stream closed 15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:309) 15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) at org.jboss.as.clustering.common@7.4.0.CD20-redhat-00001//org.jboss.as.clustering.context.ContextReferenceExecutor.execute(ContextReferenceExecutor.java:49) 15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) at org.jboss.as.clustering.common@7.4.0.CD20-redhat-00001//org.jboss.as.clustering.context.ContextualExecutor$1.run(ContextualExecutor.java:70) 15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) at java.base/java.lang.Thread.run(Thread.java:834) {code} From attached log you can see, that error message show up on the beginning of test when cluster was just forming. I have found similar issue https://issues.redhat.com/browse/JBEAP-17191.