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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.0, 6.0
• Assignee: Timothy Potter
• Reporter: Mark Miller
• Created: 21/Dec/14 03:31
• Updated: 09/May/16 18:58
• Resolved: 06/Jan/15 20:38

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.

Issue Links

• relates to: SOLR-4509 Move to non deprecated HttpClient impl classes to remove stale connection check on every request and move connection lifecycle management towards the client.