Hi Saikat, I added you as a watcher on the issue and commented there. After further review, I don't think this is really a problem, so I'll probably end up closing out the issue. Full details are in the issue comment. Thanks!
Chris Nauroth Hortonworks http://hortonworks.com/ On Wed, Jun 26, 2013 at 9:48 PM, Saikat Kanjilal <sxk1...@hotmail.com>wrote: > Is the solution for the call to block till the initialization completes? > > > Date: Thu, 27 Jun 2013 04:39:20 +0000 > > From: j...@apache.org > > To: common-dev@hadoop.apache.org > > Subject: [jira] [Created] (HADOOP-9674) RPC#Server#start does not block > until server is fully initialized and listening > > > > Chris Nauroth created HADOOP-9674: > > ------------------------------------- > > > > Summary: RPC#Server#start does not block until server is > fully initialized and listening > > Key: HADOOP-9674 > > URL: https://issues.apache.org/jira/browse/HADOOP-9674 > > Project: Hadoop Common > > Issue Type: Bug > > Components: ipc > > Affects Versions: 3.0.0, 2.2.0 > > Reporter: Chris Nauroth > > Priority: Minor > > > > > > This problem was originally mentioned in discussion on HADOOP-8980. > When calling {{RPC#Server#start}}, initialization of the server's internal > {{Listener}} and {{Reader}} threads happens in the background. This > initialization is not guaranteed to complete by the time the caller returns > from {{RPC#Server#start}}. This may be misleading to a caller that expects > the server has been fully initialized. This problem sometimes manifests as > a test failure in {{TestRPC#testStopsAllThreads}}. This test looks at the > stack frames of all running threads, expecting to find the {{Listener}} and > {{Reader}} threads, but sometimes it doesn't find them. > > > > -- > > This message is automatically generated by JIRA. > > If you think it was sent incorrectly, please contact your JIRA > administrators > > For more information on JIRA, see: > http://www.atlassian.com/software/jira > >
