[jira] [Created] (IGNITE-12419) JCache TCK fails with NullPointerException

["Vyacheslav Koptilin (Jira)" <ji...@apache.org>]

Vyacheslav Koptilin created IGNITE-12419:
--------------------------------------------

             Summary: JCache TCK fails with NullPointerException
                 Key: IGNITE-12419
                 URL: https://issues.apache.org/jira/browse/IGNITE-12419
             Project: Ignite
          Issue Type: Bug
          Components: cache
    Affects Versions: 2.7.6
            Reporter: Vyacheslav Koptilin
            Assignee: Vyacheslav Koptilin
             Fix For: 2.8


It seems a long period of time, JCache suite did not run TCK tests and for now, more than 90 tests are broken with the following exception:
{code:java}
class org.apache.ignite.IgniteCheckedException: Cannot enable read-through (loader or store is not provided) for cache: cache-loader-testclass org.apache.ignite.IgniteCheckedException: Cannot enable read-through (loader or store is not provided) for cache: cache-loader-test at org.apache.ignite.internal.processors.cache.ValidationOnNodeJoinUtils.validate(ValidationOnNodeJoinUtils.java:348) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCacheContext(GridCacheProcessor.java:1190) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheContext(GridCacheProcessor.java:1984) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1915) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCaches$55a0e703$1(GridCacheProcessor.java:1790) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.lambda$prepareStartCachesIfPossible$9(GridCacheProcessor.java:1760) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCaches(GridCacheProcessor.java:1787) at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareStartCachesIfPossible(GridCacheProcessor.java:1758) at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processCacheStartRequests(CacheAffinitySharedManager.java:968) at org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:854) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:1281) at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:811) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3172) at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:3021) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) at java.lang.Thread.run(Thread.java:748)
{code}
It looks like, the root cause of the failure is IGNITE-1903. At first glance, it can be easily fixed.
I think that cache configuration initialization should be done before it is split by {{CacheConfigurationSplitter - GridCacheProcessor.prepareCacheChangeRequest()}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)