cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patricio Echague (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3244) JDBC CassandraConnection may lead to memory leak when used in a pool
Date Thu, 29 Sep 2011 19:43:45 GMT


Patricio Echague commented on CASSANDRA-3244:

Rick, looking again at JDBCTemplate, I realized that Spring closes automatically the Statement.
And since you added a method to remove the statement from the connection once the statement
is closed, I think it should be ok for now.
> JDBC CassandraConnection may lead to memory leak when used in a pool
> --------------------------------------------------------------------
>                 Key: CASSANDRA-3244
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Drivers
>    Affects Versions: 1.0.0
>            Reporter: Patricio Echague
>            Assignee: Rick Shaw
>            Priority: Minor
>              Labels: JDBC
>             Fix For: 0.8.7
>         Attachments: 3244-v1.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