You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by tledkov-gridgain <gi...@git.apache.org> on 2016/05/12 14:42:52 UTC

[GitHub] ignite pull request: IGNITE-3090 Memory leak in IgniteH2Indexing p...

GitHub user tledkov-gridgain opened a pull request:

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

    IGNITE-3090 Memory leak in IgniteH2Indexing prepared statements cache\u2026

    Add cleanupStmtCache method that is called periodically by the GridTimeoutProcessor.
    Add memory leaks unit test for specified cases.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-3090

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/712.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 #712
    
----
commit 001788808b75b3c1790b32dde5daa10a897f9530
Author: tledkov-gridgain <tl...@gridgain.com>
Date:   2016-05-12T14:40:30Z

    IGNITE-3090 Memory leak in IgniteH2Indexing prepared statements cache. Add cleanupStmtCache method that is called periodically by the GridTimeoutProcessor.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-3090 Memory leak in IgniteH2Indexing p...

Posted by tledkov-gridgain <gi...@git.apache.org>.

Github user tledkov-gridgain closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---