Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 2 Jan 2014 20:58:50 +0000 (UTC)
From: "Jared Winick (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12686783.1388430085752.33396.1388696330697@arcas>
In-Reply-To: <JIRA.12686783.1388430085752@arcas>
References: <JIRA.12686783.1388430085752@arcas>
Subject: [jira] [Commented] (ACCUMULO-2113) Verify that The Hammer approach
 to resource leak is a viable short term fix
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jared Winick commented on ACCUMULO-2113:
----------------------------------------

[~kturner] are you referring to a version that would require changes to the ThriftConnectionPool and ZooSession to make them able to shutdown their resources without these reflection and thread hacks? I wasn't planning on that in the near term, especially if there is a working, albeit ugly, way of cleaning up resources against an unpatched Accumulo 1.5.0.  Would this non-reflection version be what actually gets added to 1.4.5, 1.5.1, 1.6.0? 

FWIW, I tested the example web application on Tomcat 6.0.37 with the same successful results.

> Verify that The Hammer approach to resource leak is a viable short term fix
> ---------------------------------------------------------------------------
>
>                 Key: ACCUMULO-2113
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2113
>             Project: Accumulo
>          Issue Type: Task
>    Affects Versions: 1.4.5, 1.5.1, 1.6.0
>            Reporter: Sean Busbey
>            Assignee: Jared Winick
>            Priority: Blocker
>             Fix For: 1.4.5, 1.5.1, 1.6.0
>
>         Attachments: ACCUMULO-2113-ResourceGraph-Tomcat.png, ACCUMULO-2113-ResourceGraph.png
>
>
> ACCUMULO-1858 contains a link to a test harness for verifying that we aren't leaking resources in e.g. Tomcat.
> We need someone to take "The Hammer" approach [proposed by Keith|http://mail-archives.apache.org/mod_mbox/accumulo-dev/201312.mbox/%3CCAGUtCHrThjFW-u%2BJK%2BZYALB-qut2VNd5AH1Sb8o7UcQFUXM4xA%40mail.gmail.com%3E] and verify that it successfully stops the leak.
> Afterwords, results should be linked to on the mailing list so we can come to consensus on how to handle the API change for releases.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)