[
https://issues.apache.org/jira/browse/IGNITE-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728943#comment-14728943
]
Semen Boikov commented on IGNITE-1366:
--------------------------------------
Found another issue which would be good to fix as part of this ticket: test
IgniteCacheP2pUnmarshallingErrorTest hangs from time to time on scan query
execution:
{noformat}
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryFutureAdapter.next(GridCacheQueryFutureAdapter.java:171)
at
org.apache.ignite.internal.processors.cache.portable.CacheObjectPortableProcessorImpl.onUtilityCacheStarted(CacheObjectPortableProcessorImpl.java:361)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:885)
{noformat}
Looks like this can happen because scan request message can arrive on node
before message listener is registered.
> Start CacheProcessor before QueryProcessor
> ------------------------------------------
>
> Key: IGNITE-1366
> URL: https://issues.apache.org/jira/browse/IGNITE-1366
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Reporter: Semen Boikov
> Assignee: Semen Boikov
> Priority: Critical
> Fix For: ignite-1.5
>
>
> Now QueryProcessor is started before CacheProcessor. With this order cache
> processor can be stopped at the moment when query request is processed, and
> this causes sporadic errors like NPE (I see this from time to time in
> IgniteCacheQueryNodeRestartSelfTest).
> Looks like cache processor does not need QueryProcessor when it's 'start'
> method is called so I think start order should be changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
