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

Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2015/09/02 12:18:45 UTC

[jira] [Created] (IGNITE-1355) Potential NPE in CacheAffinityProxy

Semen Boikov created IGNITE-1355:
------------------------------------

             Summary: Potential NPE in CacheAffinityProxy
                 Key: IGNITE-1355
                 URL: https://issues.apache.org/jira/browse/IGNITE-1355
             Project: Ignite
          Issue Type: Bug
          Components: cache
    Affects Versions: ignite-1.4
            Reporter: Semen Boikov
            Assignee: Yakov Zhdanov
             Fix For: ignite-1.5


NPE was observed on TC:
{noformat}
java.lang.NullPointerException
    at org.apache.ignite.internal.processors.affinity.GridAffinityProcessor$AffinityInfo.access$1800(GridAffinityProcessor.java:537)
    at org.apache.ignite.internal.processors.affinity.GridAffinityProcessor$CacheAffinityProxy.mapPartitionToPrimaryAndBackups(GridAffinityProcessor.java:879)
    at org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:423)
    at org.apache.ignite.internal.processors.cache.distributed.dht.IgniteCacheCrossCacheTxFailoverTest.crossCacheTxFailover(IgniteCacheCrossCacheTxFailoverTest.java:355)
{noformat}

As I see method CacheAffinityProxy.cache() can return null, but there are no checks for null.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)