[
https://issues.apache.org/jira/browse/IGNITE-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278303#comment-16278303
]
ASF GitHub Bot commented on IGNITE-7095:
----------------------------------------
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/3141
IGNITE-7095: close & cleanup internal H2 JDBC Connection
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7095
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3141.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3141
----
commit 398c18657761a8a7a415edc059862870c339a664
Author: tledkov-gridgain <[email protected]>
Date: 2017-12-05T09:43:59Z
IGNITE-7095: close & cleanup internal H2 JDBC Connection
----
> JdbcConnection hard linked in IgniteH2Indexing preventing old connections
> from closing
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-7095
> URL: https://issues.apache.org/jira/browse/IGNITE-7095
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.3
> Reporter: Alexandr Kuramshin
> Assignee: Taras Ledkov
> Fix For: 2.4, 2.5
>
> Attachments: IndexClientTest.java, IndexTest.java
>
>
> Every time a new thread performs {{SqlFieldsQuery}} the new
> {{org.h2.jdbc.JdbcConnection}} will be created and added to the
> {{org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing#conns}}.
> Such hard link prevents from the {{org.h2.util.CloseWatcher}} to be enqueued
> and old connections will remain in heap even after the thread exits.
> After some number of SQL queries the {{java.lang.OutOfMemoryError}} will
> occur.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
