You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2014/12/21 04:31:13 UTC

[jira] [Created] (SOLR-6874) There is a race around SocketProxy binding to it's port the way we setup JettySolrRunner and SocketProxy.

Mark Miller created SOLR-6874:
---------------------------------

             Summary: There is a race around SocketProxy binding to it's port the way we setup JettySolrRunner and SocketProxy.
                 Key: SOLR-6874
                 URL: https://issues.apache.org/jira/browse/SOLR-6874
             Project: Solr
          Issue Type: Bug
            Reporter: Mark Miller
            Assignee: Mark Miller


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org