Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 62E7AC11A for ; Sun, 30 Jun 2013 17:37:25 +0000 (UTC) Received: (qmail 23135 invoked by uid 500); 30 Jun 2013 17:37:24 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 23007 invoked by uid 500); 30 Jun 2013 17:37:21 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 22863 invoked by uid 99); 30 Jun 2013 17:37:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Jun 2013 17:37:20 +0000 Date: Sun, 30 Jun 2013 17:37:20 +0000 (UTC) From: "Chris Nauroth (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HADOOP-9674) RPC#Server#start does not block until server is fully initialized and listening MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-9674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth resolved HADOOP-9674. ----------------------------------- Resolution: Not A Problem As per prior comments, this doesn't appear to be a real problem in practice, so I'm resolving it as not a problem. > 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 > Assignee: 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