[
https://issues.apache.org/jira/browse/SOLR-13869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16959182#comment-16959182
]
Chris M. Hostetter commented on SOLR-13869:
-------------------------------------------
blocked by SOLR-13870, removing the sole usage of this method in solr tests.
> deprecated and remove SolrTestCaseJ4.getNextAvailablePort
> ---------------------------------------------------------
>
> Key: SOLR-13869
> URL: https://issues.apache.org/jira/browse/SOLR-13869
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Chris M. Hostetter
> Assignee: Chris M. Hostetter
> Priority: Major
>
> {{SolrTestCaseJ4.getNextAvailablePort()}} is a problematic method in that the
> entire premise assumes that since the OS allowed us to bind to a port once,
> it will allow us to re-bind to that port again at some future point in the
> text execution -- but that is not garunteed, as soon as
> getNextAvailablePort() releases the port assigned to {{new ServerSocket(0)}}
> the OS may allocate that port to some other process.
> We should deprecate & remove this method {{getNextAvailablePort()}} to
> prevent tests from adopting this bad pattern.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
