Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-3691

Make client side Connection refused error TRACE

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Duplicate
    • Icon: Minor Minor
    • 7.0.0.Final
    • 6.0.0.Final
    • Remote Protocols
    • None

      After solving ISPN-3454, it seems that only remaining client-side error during node crashes is "Connection refused":

      https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/RESILIENCE/job/jdg-func-resilience-dist-4-3/97/artifact/report/loganalysis/client/categories/cat10_entry0.txt

      This has been reported before as ISPN-1794 or ISPN-1119, but actually it seems like it reappeared in different place.

      Sorry for not reporting sooner, I got used to ignoring some of the long-open cosmetic low-prio log message issues, that I forgot about this one...

      The issue here is that these "Connection refused" problems are retry-able, so the client log shouldn't contain error.
      Maybe only some info level message about failing over to different node. But that's actually already reported by the INFO level messages about the topology changes

              rh-ee-galder Galder Zamarreño
              mlinhard Michal Linhard (Inactive)
              Archiver:
              rhn-support-adongare Amol Dongare
              Michal Linhard Michal Linhard (Inactive)

                Created:
                Updated:
                Resolved:
                Archived: