[
https://issues.apache.org/jira/browse/IGNITE-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528088#comment-15528088
]
Jason Man commented on IGNITE-3413:
-----------------------------------
Hi Alexander, fixing this seem to have introduced a NullPointerException in a
slightly different scenario. I have filed issue IGNITE-3984 with the
description of a scenario I encountered.
> Node is not started if continuous query remote filter class is not found
> ------------------------------------------------------------------------
>
> Key: IGNITE-3413
> URL: https://issues.apache.org/jira/browse/IGNITE-3413
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.6
> Reporter: Valentin Kulichenko
> Fix For: 1.7
>
> Attachments: ContQueryTest.java
>
>
> Test attached.
> The scenario is the following:
> * First node starts with the special attribute and creates a cache with the
> node filter that allows to deploy it only on nodes with this attribute.
> * Continuous query with a remote filter is executed.
> * Second node without the attribute is started. It doesn't have the remote
> filter class, the factory throws an exception and the node doesn't start at
> all, regardless of the fact that it doesn't even has the cache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
