Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 212C5200C5C for ; Thu, 20 Apr 2017 23:54:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1FFEE160B90; Thu, 20 Apr 2017 21:54:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 54D97160BB0 for ; Thu, 20 Apr 2017 23:54:09 +0200 (CEST) Received: (qmail 34376 invoked by uid 500); 20 Apr 2017 21:54:08 -0000 Mailing-List: contact issues-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list issues@hive.apache.org Received: (qmail 34157 invoked by uid 99); 20 Apr 2017 21:54:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Apr 2017 21:54:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id DE2A5CB9E6 for ; Thu, 20 Apr 2017 21:54:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 5FMzv2RaWHZ5 for ; Thu, 20 Apr 2017 21:54:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 8BC8F5FCE2 for ; Thu, 20 Apr 2017 21:54:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C9F65E0D4D for ; Thu, 20 Apr 2017 21:54:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2FA4C21B5A for ; Thu, 20 Apr 2017 21:54:04 +0000 (UTC) Date: Thu, 20 Apr 2017 21:54:04 +0000 (UTC) From: =?utf-8?Q?Sergio_Pe=C3=B1a_=28JIRA=29?= To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-16213) ObjectStore can leak Queries when rollbackTransaction throws an exception MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 20 Apr 2017 21:54:10 -0000 [ https://issues.apache.org/jira/browse/HIVE-16213?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1597= 7621#comment-15977621 ]=20 Sergio Pe=C3=B1a commented on HIVE-16213: ------------------------------------ The patch looks good [~vihangk1].=20 +1 > ObjectStore can leak Queries when rollbackTransaction throws an exception > ------------------------------------------------------------------------- > > Key: HIVE-16213 > URL: https://issues.apache.org/jira/browse/HIVE-16213 > Project: Hive > Issue Type: Bug > Components: Hive > Reporter: Alexander Kolbasov > Assignee: Vihang Karajgaonkar > Attachments: HIVE-16213.01.patch > > > In ObjectStore.java there are a few places with the code similar to: > {code} > Query query =3D null; > try { > openTransaction(); > query =3D pm.newQuery(Something.class); > ... > commited =3D commitTransaction(); > } finally { > if (!commited) { > rollbackTransaction(); > } > if (query !=3D null) { > query.closeAll(); > } > } > {code} > The problem is that rollbackTransaction() may throw an exception in which= case query.closeAll() wouldn't be executed.=20 > The fix would be to wrap rollbackTransaction in its own try-catch block. -- This message was sent by Atlassian JIRA (v6.3.15#6346)