[ https://issues.apache.org/jira/browse/ACCUMULO-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325232#comment-15325232 ]
Richard W. Eggert II commented on ACCUMULO-1379: ------------------------------------------------ This issue is marked as Fixed, but I can find no evidence of it in the Git master branch or 1.6.0 tag, nor does the "close" method appear in the published Javadocs. What gives? > 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 > > Attachments: ACCUMULO-1379.patch, ACCUMULO-1379_v2.patch, > ACCUMULO-1379_v3.patch > > > 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 was sent by Atlassian JIRA (v6.3.4#6332)