ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11524) Memory leak caused by executing a jdbc prepared statement
Date Tue, 19 Mar 2019 07:36:00 GMT

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

Vladimir Ozerov commented on IGNITE-11524:
------------------------------------------

[~tledkov-gridgain], I meant only client part. This is true that we should not send any additional
close requests to the server. This point was to clear collection of statements as they are
not viable anymore, so no need to keep inside {{Connection}}.

> Memory leak caused by executing a jdbc prepared statement
> ---------------------------------------------------------
>
>                 Key: IGNITE-11524
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11524
>             Project: Ignite
>          Issue Type: Bug
>          Components: jdbc, sql
>            Reporter: Pavel Vinokurov
>            Assignee: Taras Ledkov
>            Priority: Blocker
>             Fix For: 2.8
>
>         Attachments: PreparedStatementOOMReproducer.java
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Executing a prepared statement multiple times lead to OOM.
> VisualVM indicates that heap contains  a lot of JdbcThinPreparedStatament objects.
> The reproducer is attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message