[
https://issues.apache.org/jira/browse/THRIFT-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531992#comment-14531992
]
James E. King, III commented on THRIFT-1944:
--------------------------------------------
This appears to have been fixed in Java and in C++ in version 0.9.2.
I changed the TServerIntegrationTest in THRIFT-3130 so that it runs some of the
tests with a port number of zero and queries it with getPort(), and it passes
(see line 166 in TServerIntegrationTest.cpp changes at
https://github.com/jeking3/thrift/commit/929a7453034ef55434281908b3050b438c543da0).
Can this be closed or is this something where we need 13 more subtasks, one for
each language, or do we resolve it and set the fix version?
> Binding to zero port
> --------------------
>
> Key: THRIFT-1944
> URL: https://issues.apache.org/jira/browse/THRIFT-1944
> Project: Thrift
> Issue Type: Improvement
> Components: C++ - Library
> Affects Versions: 0.9
> Environment: All platforms
> Reporter: Akshat Aranya
> Assignee: Ben Craig
> Labels: bind
> Attachments: patch-THRIFT-1944-java.patch,
> patch-THRIFT-1944-updated.patch, patch-THRIFT-1944.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> This patch builds upon a previously submitted patch that was not accepted
> (THRIFT-966). The purpose of this patch is to allow TServerSocket to bind to
> port zero, that is, have the server socket be assigned a port by the OS.
> This patch provides a way to query the port after the socket has been bound
> and determine the OS assigned port
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
