[ 
https://issues.apache.org/jira/browse/ACCUMULO-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825676#comment-13825676
 ] 

ASF subversion and git services commented on ACCUMULO-1379:
-----------------------------------------------------------

Commit 79d686faa1e477b9cbd80c6f833ece402050b490 in branch 
refs/heads/1.5.1-SNAPSHOT from [~busbey]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=79d686f ]

ACCUMULO-1858 Backport ZooKeeper clean up to 1.4 and 1.5.

Fix cherry picks two commits:

ACCUMULO-1379 - Adding close() to Instance to assist in freeing up resources

(cherry picked from commit 7da1164d87227960d3e0cfc841f753067e2c0304)

Reason: bugfix
Author: John Vines <jvi...@gmail.com>

Differs from original by path changes and leaving out ConditionalWriterTest, 
which is only in 1.6.0+

----

ACCUMULO-1379 Fix edge cases if error in closing ZooKeeperInstance

(cherry picked from commit 3f6c66ede52cb1fb5a122d7bad06d7978ff0a671)

Reason: bugfix
Author: Christopher Tubbs <ctubb...@apache.org>

Signed-off-by: Bill Slacum <ujustgotbi...@apache.org>


>  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.1#6144)

Reply via email to