You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/10/27 01:12:20 UTC

[jira] Resolved: (CASSANDRA-1665) JMX threads leak in NodeProbe

     [ https://issues.apache.org/jira/browse/CASSANDRA-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-1665.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.7.1
         Reviewer: jbellis
         Assignee: Bill Au

committed, thanks!

> JMX threads leak in NodeProbe
> -----------------------------
>
>                 Key: CASSANDRA-1665
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1665
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 0.7.0
>            Reporter: Bill Au
>            Assignee: Bill Au
>            Priority: Minor
>             Fix For: 0.7.1
>
>         Attachments: trunk-1665.txt
>
>
> There is a JMX threads leak in NodeProbe.  It creates and uses a JMXConnector but never calls its close() method.  I am working on a patch which add a close() method to NodeProbe  that calls JMXConnector.close().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.