Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-6874

There is a race around SocketProxy binding to it's port the way we setup JettySolrRunner and SocketProxy.

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0, 6.0
    • Component/s: None
    • Labels:
      None

      Description

      I ran into this while working on SOLR-4509 and have a fix there in my latest patch. Because we get an available port by opening and closing a scocket on port 0 and then try to use it again with the SocketProxy, sometimes it fails to bind and the test can fail. We can change the code a bit so that the SocketProxy itself can start on port 0 rather than this two step fragile process.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              thelabdude Timothy Potter
              Reporter:
              markrmiller@gmail.com Mark Miller

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment