[
https://issues.apache.org/jira/browse/PHOENIX-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178540#comment-14178540
]
James Taylor commented on PHOENIX-1364:
---------------------------------------
[[email protected]] - is the pom change necessary? Maybe we can move the pom
change to a separate JIRA?
Do you think this might fix the "endless tracing" we see on the server-side,
[~jesse_yates]?
> Fix resource leaks in various classes
> -------------------------------------
>
> Key: PHOENIX-1364
> URL: https://issues.apache.org/jira/browse/PHOENIX-1364
> Project: Phoenix
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 1364-v2.txt, fix-resource-leak-v1.txt
>
>
> Statement / PreparedStatement should be closed after query completes.
> Below is an example of resource leak from
> MetaDataUtil#deleteViewIndexSequences():
> {code}
> public static void deleteViewIndexSequences(PhoenixConnection
> connection, PName name) throws SQLException {
> SequenceKey key = getViewIndexSequenceKey(null, name);
> connection.createStatement().executeUpdate("DELETE FROM " +
> PhoenixDatabaseMetaData.SEQUENCE_TABLE_NAME +
> {code}
> The Statement created by connection.createStatement() should be closed upon
> return.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
