You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2014/10/21 20:34:34 UTC

[jira] [Updated] (PHOENIX-1364) Close tracing scope to stop excessive tracing

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

Ted Yu updated PHOENIX-1364:
----------------------------
    Summary: Close tracing scope to stop excessive tracing  (was: Fix resource leaks in various classes)

> Close tracing scope to stop excessive tracing
> ---------------------------------------------
>
>                 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, 1364-v3.patch, 1364-v4.patch, 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)