Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-19902

Intermittent error message in log "java.io.IOException: Stream closed"

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Trivial
    • None
    • 7.4.0.CD20
    • Clustering, OpenShift
    • None

    Description

      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?

      �[0m�[31m15: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
�[0m�[31m15: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)
�[0m�[31m15: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)
�[0m�[31m15: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)
�[0m�[31m15: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)

      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.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JGRP-2489 TcpConnection.Receiver#run should use logger to handle exception rather than rely on the UncaughtExceptionHandler

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          is incorporated by

          Release - A container task to coordinate the tasks for a given release. JBEAP-19839 EAP CD 20 OpenShift Image Release

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • New

          Tracker - Issue tracking a bug fix or improvement in another component JBEAP-17060 OpenShift HA Tests Stabilisation Tracker

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Release - A container task to coordinate the tasks for a given release. JBEAP-19839 EAP CD 20 OpenShift Image Release

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • New

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) CLOUD-3670 EAP CD 20 OpenShift Image Release

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-engineering-rhusar Radoslav Husar
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: