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

Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2015/01/03 00:36:35 UTC

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

    [ https://issues.apache.org/jira/browse/SOLR-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14263317#comment-14263317 ] 

Shalin Shekhar Mangar commented on SOLR-6874:
---------------------------------------------

+1 to commit.

This resolves the failures seen in SOLR-4839 as well.

> 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
>         Attachments: SOLR-6874.patch
>
>
> 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