accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jared Winick (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2113) Verify that The Hammer approach to resource leak is a viable short term fix
Date Thu, 02 Jan 2014 18:36:03 GMT

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

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

[~kturner] agreed - it is quite ugly as is. I just determined a big issue with the implementation
that uses Thread.stop(). If multiple web applications are deployed to the same application
server, and thus are running in the same JVM, the posted implementation will kill all the
"Thrift Connection Pool Checker" threads from all deployed web applications. Clearly this
make it an unacceptable implementation.

> 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.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)

Mime
View raw message