Re: Best way to fix JMX threads leak in NodeProbe

2010-10-26 Thread Bill Au
I have opened a jira for this issue: https://issues.apache.org/jira/browse/CASSANDRA-1665 I will submit a patch. Bill On Tue, Oct 26, 2010 at 12:21 PM, Jonathan Ellis wrote: > Yes, we should add a close method. > On Oct 26, 2010 9:14 AM, "Bill Au" wrote: > > I have discovered a JMX threads l

Re: Best way to fix JMX threads leak in NodeProbe

2010-10-26 Thread Jonathan Ellis
Yes, we should add a close method. On Oct 26, 2010 9:14 AM, "Bill Au" wrote: > I have discovered a JMX threads leak in NodeProbe. Here is the original > email thread on the user mailing list: > > http://www.mail-archive.com/u...@cassandra.apache.org/msg06764.html > > NodePorbe creats a JMXConnecto

Best way to fix JMX threads leak in NodeProbe

2010-10-26 Thread Bill Au
I have discovered a JMX threads leak in NodeProbe. Here is the original email thread on the user mailing list: http://www.mail-archive.com/u...@cassandra.apache.org/msg06764.html NodePorbe creats a JMXConnector but never calls JMXConnector.close(). The use of a JMXConnector in NodeProbe is not