calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jingwu Li (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CALCITE-1739) backend jdbc connection does not returned to connection pool after execute a query.
Date Mon, 03 Apr 2017 18:12:41 GMT
Jingwu Li created CALCITE-1739:
----------------------------------

             Summary: backend jdbc connection does not returned to connection pool after execute
a query.
                 Key: CALCITE-1739
                 URL: https://issues.apache.org/jira/browse/CALCITE-1739
             Project: Calcite
          Issue Type: Bug
          Components: core
         Environment: JDK 8
            Reporter: Jingwu Li
            Assignee: Julian Hyde


When we use calcite jdbc adapter to connect to backend database like Oracles, after running
query, the connection does not get returned to connection pool after execution. The apache
jdbc dbcp connection pool default max connection is 8. So after running a couple times of
queries, all connections got used, the new request got hang due to not able to get hold of
a free connection. 

In org.apache.calcite.runtime.ResultSetEnumerable class
line 146         statement = null;
147               connection = null;
 should we remove those lines so in the finally block the connection.close(); can be executed?




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message