ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-7095) JdbcConnection hard linked in IgniteH2Indexing preventing old connections from closing
Date Tue, 12 Dec 2017 13:23:01 GMT

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

ASF GitHub Bot commented on IGNITE-7095:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/3141


> 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
>
>         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)

Mime
View raw message