Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3466

No error reported when remote handshake fails

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 11.0.0.Final
    • 8.0.0.Final, 8.1.0.Final
    • Remoting
    • None
    • Hide

      This is easily reproducible by blocking the incoming request on the destination's server side. I used a packet sniffer to see a TCP request was sent but then immediately sent again with RST flag (indicating no delivery).

      Show
      This is easily reproducible by blocking the incoming request on the destination's server side. I used a packet sniffer to see a TCP request was sent but then immediately sent again with RST flag (indicating no delivery).

    Description

      When the destination server fails to respond and thus the remote handshake cannot be made, nothing gets reported in the client's log – even when put on TRACE. I spent many days trying to get to the bottom of this. This abnormal condition is too important for it to go unreported.

      Attachments

        Activity

          People

            dlloyd@redhat.com David Lloyd
            paul.benedict Paul Benedict
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: