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 49DCE200C70 for ; Thu, 4 May 2017 18:24:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 487CD160BC5; Thu, 4 May 2017 16:24:08 +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 8E804160B9F for ; Thu, 4 May 2017 18:24:07 +0200 (CEST) Received: (qmail 84953 invoked by uid 500); 4 May 2017 16:24:06 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 84933 invoked by uid 99); 4 May 2017 16:24:06 -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, 04 May 2017 16:24:06 +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 E6974C9D63 for ; Thu, 4 May 2017 16:24:05 +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-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id jwJ15UO-uCWU for ; Thu, 4 May 2017 16:24:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 3F9005FD29 for ; Thu, 4 May 2017 16:24: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 7171AE008E for ; Thu, 4 May 2017 16:24: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 2DF1C21DE0 for ; Thu, 4 May 2017 16:24:04 +0000 (UTC) Date: Thu, 4 May 2017 16:24:04 +0000 (UTC) From: "Ryan Fong (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (JCS-177) CompositeCacheManager leaks memory if CacheAccess.dipose is called MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 04 May 2017 16:24:08 -0000 [ https://issues.apache.org/jira/browse/JCS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Fong updated JCS-177: -------------------------- Attachment: jcs-test.zip jcs-177.patch I have attached one possible solution that should fix this problem as jcs-177.patch. An alternative to this is to have a pointer from CompositeCache to CompositeCacheManager so we do not incur the overhead of incrementing and decrementing the client count. Also find an Eclipse project that uses stock 2.1 to demonstrate how the leak occurs and how CompositeCacheManager.freeCache avoids this issue. > CompositeCacheManager leaks memory if CacheAccess.dipose is called > ------------------------------------------------------------------ > > Key: JCS-177 > URL: https://issues.apache.org/jira/browse/JCS-177 > Project: Commons JCS > Issue Type: Bug > Affects Versions: jcs-2.1 > Reporter: Ryan Fong > Priority: Critical > Attachments: jcs-177.patch, jcs-test.zip > > > In JCS 2.1, The org.apache.commons.jcs.engine.control.CompositeCacheManager holds onto a reference of CacheAccess in its caches map. If CacheAccess.dispose is called, this reference is not cleaned up which results in a memory leak. -- This message was sent by Atlassian JIRA (v6.3.15#6346)