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 21F28200C02 for ; Fri, 20 Jan 2017 10:33:33 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 209D3160B39; Fri, 20 Jan 2017 09:33:33 +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 6B5A0160B48 for ; Fri, 20 Jan 2017 10:33:32 +0100 (CET) Received: (qmail 11400 invoked by uid 500); 20 Jan 2017 09:33:31 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 11391 invoked by uid 99); 20 Jan 2017 09:33:31 -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; Fri, 20 Jan 2017 09:33:31 +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 36E21C14DA for ; Fri, 20 Jan 2017 09:33:31 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] 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 BdBPZ6Z4qm3Q for ; Fri, 20 Jan 2017 09:33:30 +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 E5FC05FB5D for ; Fri, 20 Jan 2017 09:33:29 +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 BF0CCE008E for ; Fri, 20 Jan 2017 09:33:26 +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 669192527F for ; Fri, 20 Jan 2017 09:33:26 +0000 (UTC) Date: Fri, 20 Jan 2017 09:33:26 +0000 (UTC) From: "Andrew Mashenkov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-4578) SQL: Statement cache can cause memory leak MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 20 Jan 2017 09:33:33 -0000 Andrew Mashenkov created IGNITE-4578: ---------------------------------------- Summary: SQL: Statement cache can cause memory leak Key: IGNITE-4578 URL: https://issues.apache.org/jira/browse/IGNITE-4578 Project: Ignite Issue Type: Bug Components: SQL Affects Versions: 1.8 Reporter: Andrew Mashenkov We have prepared statement cache in IgniteH2Indexing declared as Map. This can cause memory leak if threads will die unexpetedly. We should declare StatementCache as ThreadLocal field along with separate thread pool for SQL queries, see IGNITE-4105. -- This message was sent by Atlassian JIRA (v6.3.4#6332)