cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-3606) Resource Leaks in code
Date Tue, 24 Apr 2012 18:11:33 GMT

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

Jonathan Ellis resolved CASSANDRA-3606.
---------------------------------------

    Resolution: Not A Problem

Did you look at what closeQuietly does?  It will catch and log exceptions on close, so you
don't need the nested try/catch in the caller.
                
> Resource Leaks in code
> ----------------------
>
>                 Key: CASSANDRA-3606
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3606
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Zoltan Farkas
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> at the following locations:
> At SSLFactory:[line 87]
> At SSTableExportTest:[line 83]
> At CommitLogTest:[line 191]
> At KeyGenerator:[line 108]
> At Ec2Snitch.java:[line 74]
> At SSTableExportTest.java:[line 83]
> At CassandraServer.java:[line 1164]
> At CommitLogTest.java:[line 191]
> At ByteBufferUtilTest.java:[line 194]
> At LazilyCompactedRowTest.java:[line 108]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message