You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2015/09/03 16:07:45 UTC

[jira] [Commented] (IGNITE-1365) Unable to deserialize object because class ID key is not in the cache

    [ https://issues.apache.org/jira/browse/IGNITE-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729109#comment-14729109 ] 

Denis Magda commented on IGNITE-1365:
-------------------------------------

Haven't managed to reproduce locally on both windows and linux machines.

Reproduced only on TC. Created a special test suite for this, will keep investigating.
http://94.72.60.102/viewLog.html?buildId=530142&tab=buildResultsDiv&buildTypeId=IgniteGridGain_TempTestSuite

> Unable to deserialize object because class ID key is not in the cache
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-1365
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1365
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: ignite-1.4
>            Reporter: Denis Magda
>            Assignee: Denis Magda
>            Priority: Critical
>
> There is a test that fails because of object deserialization issue:
> http://204.14.53.153/viewLog.html?buildId=65291&tab=buildResultsDiv&buildTypeId=Ignite_IgniteBasic#testNameId7413691472559096192
> According to the log, the reason of the failure is the following:
> {noformat}
> Caused by: class org.apache.ignite.internal.cluster.ClusterTopologyServerNotFoundException: Failed to map keys for cache (all partition nodes left the grid).
>     at org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.map(GridPartitionedGetFuture.java:308)
>     at org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture.init(GridPartitionedGetFuture.java:199)
>     at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAllAsync0(GridDhtAtomicCache.java:1048)
>     at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1300(GridDhtAtomicCache.java:124)
>     at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$10.apply(GridDhtAtomicCache.java:336)
>     at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$10.apply(GridDhtAtomicCache.java:334)
>     at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(GridDhtAtomicCache.java:648)
>     at org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.getAllAsync(GridDhtAtomicCache.java:334)
>     at org.apache.ignite.internal.processors.cache.GridCacheAdapter.getTopologySafe(GridCacheAdapter.java:1345)
>     at org.apache.ignite.internal.MarshallerContextImpl.className(MarshallerContextImpl.java:148)
>     at org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
>     at org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:256)
> {noformat}
> However, if to take a look at the test code we will see that this situation is impossible: all the nodes should be alive during the test's execution.
> It means that the issue is somewhere in {{GridCacheAdapter.getTopologySafe}} implementation.



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