[
https://issues.apache.org/jira/browse/IGNITE-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Veselovsky updated IGNITE-1691:
------------------------------------
Description:
The problem is that c.context().config() returns null after the cache was
cleaned up.
{code} for (IgniteCacheProxy<?, ?> c : g0.context().cache().jcaches()) {
CacheConfiguration cfg = c.context().config(); // *** cfg ==
null there {code}
{code}
java.lang.NullPointerException: null
at
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:416)
at
org.apache.ignite.internal.processors.cache.CacheStopAndDestroySelfTest.checkDestroyed(CacheStopAndDestroySelfTest.java:754)
at
org.apache.ignite.internal.processors.cache.CacheStopAndDestroySelfTest.dhtDestroy(CacheStopAndDestroySelfTest.java:226)
at
org.apache.ignite.internal.processors.cache.CacheStopAndDestroySelfTest.testDhtDoubleDestroy(CacheStopAndDestroySelfTest.java:199)
{code}
Hint: to achieve better reproducibility repeat dhtDestroy(); operation in the
test not 2, but several tens times.
was:
The problem is that c.context().config() returns null after the cache was
cleaned up.
for (IgniteCacheProxy<?, ?> c : g0.context().cache().jcaches()) {
CacheConfiguration cfg = c.context().config();
java.lang.NullPointerException: null
at
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:416)
at
org.apache.ignite.internal.processors.cache.CacheStopAndDestroySelfTest.checkDestroyed(CacheStopAndDestroySelfTest.java:754)
at
org.apache.ignite.internal.processors.cache.CacheStopAndDestroySelfTest.dhtDestroy(CacheStopAndDestroySelfTest.java:226)
at
org.apache.ignite.internal.processors.cache.CacheStopAndDestroySelfTest.testDhtDoubleDestroy(CacheStopAndDestroySelfTest.java:199)
Hint: to achieve better reproducibility repeat dhtDestroy(); operation in the
test not 2, but several tens times.
> [Test] CacheStopAndDestroySelfTest.testDhtDoubleDestroy fails with NPE
> sometimes.
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-1691
> URL: https://issues.apache.org/jira/browse/IGNITE-1691
> Project: Ignite
> Issue Type: Test
> Reporter: Ivan Veselovsky
>
> The problem is that c.context().config() returns null after the cache was
> cleaned up.
> {code} for (IgniteCacheProxy<?, ?> c : g0.context().cache().jcaches()) {
> CacheConfiguration cfg = c.context().config(); // *** cfg ==
> null there {code}
> {code}
> java.lang.NullPointerException: null
> at
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:416)
> at
> org.apache.ignite.internal.processors.cache.CacheStopAndDestroySelfTest.checkDestroyed(CacheStopAndDestroySelfTest.java:754)
> at
> org.apache.ignite.internal.processors.cache.CacheStopAndDestroySelfTest.dhtDestroy(CacheStopAndDestroySelfTest.java:226)
> at
> org.apache.ignite.internal.processors.cache.CacheStopAndDestroySelfTest.testDhtDoubleDestroy(CacheStopAndDestroySelfTest.java:199)
> {code}
> Hint: to achieve better reproducibility repeat dhtDestroy(); operation in the
> test not 2, but several tens times.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
