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 5A9334B71 for ; Tue, 5 Jul 2011 15:11:43 +0000 (UTC) Received: (qmail 17816 invoked by uid 500); 5 Jul 2011 15:11:42 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 17214 invoked by uid 500); 5 Jul 2011 15:11:41 -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 17174 invoked by uid 99); 5 Jul 2011 15:11:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jul 2011 15:11:41 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jul 2011 15:11:37 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id E260943BCB for ; Tue, 5 Jul 2011 15:11:16 +0000 (UTC) Date: Tue, 5 Jul 2011 15:11:16 +0000 (UTC) From: "Uma Maheswara Rao G (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1070568732.859.1309878676924.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <18917644.179531294294848031.JavaMail.jira@thor> Subject: [jira] [Commented] (HADOOP-7090) Possible resource leaks in hadoop core code 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-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059943#comment-13059943 ] Uma Maheswara Rao G commented on HADOOP-7090: --------------------------------------------- difficult to assert the stream closes alone. Since all existing tests are passing with this changes , no need to have special tests for this changes. > Possible resource leaks in hadoop core code > ------------------------------------------- > > Key: HADOOP-7090 > URL: https://issues.apache.org/jira/browse/HADOOP-7090 > Project: Hadoop Common > Issue Type: Bug > Affects Versions: 0.21.0, 0.23.0 > Reporter: Gokul > Assignee: Uma Maheswara Rao G > Attachments: HADOOP-7090.0.patch, HADOOP-7090.patch > > > It is always a good practice to close the IO streams in a finally block.. > For example, look at the following piece of code in the Writer class of BloomMapFile > {code:title=BloomMapFile .java|borderStyle=solid} > public synchronized void close() throws IOException { > super.close(); > DataOutputStream out = fs.create(new Path(dir, BLOOM_FILE_NAME), true); > bloomFilter.write(out); > out.flush(); > out.close(); > } > {code} > If an exception occurs during fs.create or on any other line, out.close() will not be executed.. > The following can reduce the scope of resorce leaks.. > {code:title=BloomMapFile .java|borderStyle=solid} > public synchronized void close() throws IOException { > super.close(); > DataOutputStream out = null; > try{ > out = fs.create(new Path(dir, BLOOM_FILE_NAME), true); > bloomFilter.write(out); > out.flush(); > }finally{ > IOUtils.closeStream(out); > } > {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira