cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3244) JDBC CassandraConnection may lead to memory leak when used in a pool
Date Wed, 05 Oct 2011 20:32:29 GMT


Hudson commented on CASSANDRA-3244:

Integrated in Cassandra #1142 (See [])
    remove statements from connection's list, when closed manually
patch by Rick Shaw; reviewed by Patricio Echague and jbellis for CASSANDRA-3244

jbellis :
Files : 
* /cassandra/trunk/drivers/java/src/org/apache/cassandra/cql/jdbc/
* /cassandra/trunk/drivers/java/src/org/apache/cassandra/cql/jdbc/

> JDBC CassandraConnection may lead to memory leak when used in a pool
> --------------------------------------------------------------------
>                 Key: CASSANDRA-3244
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Drivers
>            Reporter: Patricio Echague
>            Assignee: Rick Shaw
>            Priority: Minor
>              Labels: JDBC
>         Attachments: 3244-v1.txt, 3244-v2.txt
> I may be wrong here but I noticed that the implementations of CassandraConnection#createStatement()
and CassandraConnection#prepareStatement() keep(cache) the created Statement/PrepareStatement
internally in a List.
> They list is freed up only during CassandraConnection.close() which makes me think that,
if the connection object is used in a pool implementation, it will lead to a memory leak as
it will hold every single statement that is used to interact with the DB until the connection
gets closed. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message