[
https://issues.apache.org/jira/browse/CALCITE-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539161#comment-17539161
]
itxiangkui commented on CALCITE-1739:
-------------------------------------
[~jingwuli]
Let's take a look at the CALCITE-5099 problem..
> 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
> Priority: Major
>
> 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
(v8.20.7#820007)
