cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Au (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-1665) JMX threads leak in NodeProbe
Date Tue, 26 Oct 2010 22:01:23 GMT

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

Bill Au updated CASSANDRA-1665:
-------------------------------

    Attachment: trunk-1665.txt

I have added a close() method to NodeProbe.  I have also added a close() method that calls
NodeProbe.close() to ClusterCmd since it creates its own private instance of NodeProbe in
its constructors..

> 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
>            Priority: Minor
>         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.


Mime
View raw message