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 68416951A for ; Tue, 10 Jul 2012 18:24:38 +0000 (UTC) Received: (qmail 7997 invoked by uid 500); 10 Jul 2012 18:24:36 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 7954 invoked by uid 500); 10 Jul 2012 18:24:36 -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 7855 invoked by uid 99); 10 Jul 2012 18:24:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2012 18:24:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id AC5B4142863 for ; Tue, 10 Jul 2012 18:24:35 +0000 (UTC) Date: Tue, 10 Jul 2012 18:24:35 +0000 (UTC) From: "Hadoop QA (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <358774417.29999.1341944675708.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1821643605.14353.1341587135232.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HADOOP-8573) Configuration tries to read from an inputstream resource multiple times. 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-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410659#comment-13410659 ] Hadoop QA commented on HADOOP-8573: ----------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12535885/HADOOP-8573.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 1 new or modified test files. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 javadoc. The javadoc tool did not generate any warning messages. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in hadoop-common-project/hadoop-common. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/1182//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1182//console This message is automatically generated. > Configuration tries to read from an inputstream resource multiple times. > ------------------------------------------------------------------------- > > Key: HADOOP-8573 > URL: https://issues.apache.org/jira/browse/HADOOP-8573 > Project: Hadoop Common > Issue Type: Bug > Components: conf > Affects Versions: 1.0.2, 0.23.3, 2.0.1-alpha, 3.0.0 > Reporter: Robert Joseph Evans > Assignee: Robert Joseph Evans > Attachments: HADOOP-8573.txt, HADOOP-8573.txt, HADOOP-8573.txt > > > If someone calls Configuration.addResource(InputStream) and then reloadConfiguration is called for any reason, Configruation will try to reread the contents of the InputStream, after it has already closed it. > This never showed up in 1.0 because the framework itself does not call addResource with an InputStream, and typically by the time user code starts running that might call this, all of the default and site resources have already been loaded. > In 0.23 mapreduce is now a client library, and mapred-site.xml and mapred-default.xml are loaded much later in the process. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira