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

FD_SOCK2 not always closing its server socket

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 27.0.0.Final
    • 27.0.0.Beta1
    • Clustering
    • None
    • ---
    • ---

    Description

      I suspect this might be an issue with the stop logic of NioServer, where the server socket is not getting closed, which can cause server restart/reload to fail, since we intentionally restrict the port_range to a single value.
      e.g.
      https://ci.wildfly.org/viewLog.html?buildId=329871&buildTypeId=WF_PullRequest_GalleonLinuxJdk11#testNameId-6999047029406847230

      Attachments

        Issue Links

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: