Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6B6E510BBC for ; Tue, 2 Jul 2013 21:31:20 +0000 (UTC) Received: (qmail 76668 invoked by uid 500); 2 Jul 2013 21:31:20 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 76638 invoked by uid 500); 2 Jul 2013 21:31:20 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 76629 invoked by uid 99); 2 Jul 2013 21:31:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jul 2013 21:31:20 +0000 Date: Tue, 2 Jul 2013 21:31:20 +0000 (UTC) From: "John Vines (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1379) PermGen leak 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/ACCUMULO-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698269#comment-13698269 ] John Vines commented on ACCUMULO-1379: -------------------------------------- I'm going to be handling this in the curator branch, because this also makes things a lot more pleasant in testing due to staticness of things. > PermGen leak > -------------- > > Key: ACCUMULO-1379 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1379 > Project: Accumulo > Issue Type: Bug > Components: client > Affects Versions: 1.4.3, 1.5.0 > Environment: Linux/JBoss > Reporter: Mike Giordano > Assignee: John Vines > Fix For: 1.6.0 > > > Under version 1.3.7 we are using the following code to initialize a cloudbase connection during initialization of our web app: > ZooKeeperInstance instance = new ZooKeeperInstance(instanceName, zooKeepers); > connector = instance.getConnector(userId, password.getBytes()); > The problem is that under the hood, this call creates several threads that are not cleaned up when the app is undeployed in JBoss. This is occurring without performing any scans or interacting with cloudbase in any other way. After relatively few redeploys of the app, the PermGen Space is OOM. > I can't find any reference in the cloudbase API akin to a close() method for the Connector object. This is a classloader leak effecting any webapp that is accessing cloudbase directly. The result of this leak is not simply orphaned threads, but thousands of classes not gc'd because the classloader itself can't be gc'd. This is what is filling up PermGen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira