Uploaded image for project: 'JGroups'
  1. JGroups
  2. JGRP-2489

TcpConnection.Receiver#run should use logger to handle exception rather than rely on the UncaughtExceptionHandler

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 4.2.5, 5.0.0.Final
    • 4.2.4
    • None

      An example of an exception being non-standardly thusly logged to stderr:

      �[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)
      

              rhn-engineering-rhusar Radoslav Husar
              rhn-engineering-rhusar Radoslav Husar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: