[
https://issues.apache.org/jira/browse/IGNITE-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972835#comment-15972835
]
ASF GitHub Bot commented on IGNITE-5008:
----------------------------------------
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/1822
IGNITE-5008 message of IgniteOutOfMemoryException was detailed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5008
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1822.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 #1822
----
commit d6fc207693d0928ef615cc409054af067d5a079b
Author: Sergey Chugunov <sergey.chugu...@gmail.com>
Date: 2017-04-18T14:37:59Z
IGNITE-5008 message of IgniteOutOfMemoryException was detailed
----
> Page Memory Throws Meaningless OOM exception if there is an issue in config
> ---------------------------------------------------------------------------
>
> Key: IGNITE-5008
> URL: https://issues.apache.org/jira/browse/IGNITE-5008
> Project: Ignite
> Issue Type: Bug
> Reporter: Denis Magda
> Assignee: Sergey Chugunov
> Priority: Blocker
>
> The ticket was created as a result of this discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/Memory-policies-examples-fails-td16717.html
> Presently a page memory can throw an OOM exception due to a misconfiguration.
> The message of the exception has to point out to a problematic place directly
> (size, ect.) so that the user can quickly fix it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
