[ 
https://issues.apache.org/jira/browse/PHOENIX-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178850#comment-14178850
 ] 

Hudson commented on PHOENIX-1364:
---------------------------------

SUCCESS: Integrated in Phoenix | Master #451 (See 
[https://builds.apache.org/job/Phoenix-master/451/])
PHOENIX-1364 Fix resource leaks in various classes (Ted Yu) (jtaylor: rev 
94a72a2988bd837a8584883043a9f407f208c43e)
* phoenix-core/src/main/java/org/apache/phoenix/hbase/index/Indexer.java
* 
phoenix-hadoop2-compat/src/main/java/org/apache/phoenix/trace/TraceMetricSource.java


> 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
>             Fix For: 5.0.0, 4.2
>
>         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)

Reply via email to