[
https://issues.apache.org/jira/browse/IGNITE-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190983#comment-16190983
]
ASF GitHub Bot commented on IGNITE-6536:
----------------------------------------
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/2799
IGNITE-6536 node must fail when detects mapping storage corruption
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6536
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2799.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 #2799
----
commit fa7b54bdc7c1c0290666bce2bff2d98fc9b5b972
Author: Sergey Chugunov <[email protected]>
Date: 2017-10-03T16:17:50Z
IGNITE-6536 node fails when detects mapping storage corruption
----
> NPE on registerClassName() with MappedName
> ------------------------------------------
>
> Key: IGNITE-6536
> URL: https://issues.apache.org/jira/browse/IGNITE-6536
> Project: Ignite
> Issue Type: Bug
> Components: binary
> Affects Versions: 2.1
> Reporter: Alexandr Kuramshin
> Fix For: None
>
>
> {{NullPointerException}} occurs in
> {{org.apache.ignite.internal.MarshallerContextImpl#registerClassName}} on
> trying to compare {{mappedName.className()}} of already existed {{typeId}}
> mapping with the new one {{clsName}} has come as a parameter.
> Actually
> {{org.apache.ignite.internal.processors.marshaller.MappedName#className}} may
> not be null but it was. So we should check {{clsName}} comes in
> {{MappedName}} constructor, to prevent same NPEs in the future.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
