[jira] [Updated] (CASSANDRA-3244) JDBC CassandraConnection may lead to memory leak when used in a pool
[ https://issues.apache.org/jira/browse/CASSANDRA-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-3244: -- Affects Version/s: (was: 1.0.0) Fix Version/s: (was: 0.8.8) JDBC CassandraConnection may lead to memory leak when used in a pool Key: CASSANDRA-3244 URL: https://issues.apache.org/jira/browse/CASSANDRA-3244 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3244) JDBC CassandraConnection may lead to memory leak when used in a pool
[ https://issues.apache.org/jira/browse/CASSANDRA-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Shaw updated CASSANDRA-3244: - Attachment: 3244-v2.txt JDBC CassandraConnection may lead to memory leak when used in a pool Key: CASSANDRA-3244 URL: https://issues.apache.org/jira/browse/CASSANDRA-3244 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, 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3244) JDBC CassandraConnection may lead to memory leak when used in a pool
[ https://issues.apache.org/jira/browse/CASSANDRA-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-3244: -- Reviewer: patricioe JDBC CassandraConnection may lead to memory leak when used in a pool Key: CASSANDRA-3244 URL: https://issues.apache.org/jira/browse/CASSANDRA-3244 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3244) JDBC CassandraConnection may lead to memory leak when used in a pool
[ https://issues.apache.org/jira/browse/CASSANDRA-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Shaw updated CASSANDRA-3244: - Attachment: 3244-v1.txt JDBC CassandraConnection may lead to memory leak when used in a pool Key: CASSANDRA-3244 URL: https://issues.apache.org/jira/browse/CASSANDRA-3244 Project: Cassandra Issue Type: Improvement Components: Drivers Affects Versions: 1.0.0 Reporter: Patricio Echague Priority: Minor 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
