[
https://issues.apache.org/jira/browse/IGNITE-12798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061513#comment-17061513
]
Ivan Pavlukhin commented on IGNITE-12798:
-----------------------------------------
[~rangerzhou], I guess that your problem is related to remote class loading. I
suppose that when you start servers using ignite.sh server java processes do
not have filter/listener classes on classpath. Classes need to be somehow
delivered to servers, enabling _peer class loading_ might help
(https://apacheignite.readme.io/docs/zero-deployment#peer-class-loading). Next
potential problem might be using java lambdas for _filters_ and _listeners_, it
worth trying anonymous classes if it does not work with lambdas.
> Failed to start continuous query when use client node in IDEA
> -------------------------------------------------------------
>
> Key: IGNITE-12798
> URL: https://issues.apache.org/jira/browse/IGNITE-12798
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.7.6
> Reporter: RangerZhou
> Priority: Major
> Attachments: Exception.log, Exception01.png, Exception02.png,
> Exception03.png, TOFListener.png
>
>
> I start ignite server by ./ignite.sh, start a ignite client by java code, and
> execute a continuous query with java in IDEA, but exception like this:
> Exception in thread "main" javax.cache.CacheException: Failed to start
> continuous query.
> Caused by: class org.apache.ignite.IgniteCheckedException: TOFListener
> But if I start server node by java code in IDEA ( Ignition.start() ), the
> continuous query is ok.
> My client code as below:
>
> !TOFListener.png!
> The exception screenshots:
> !Exception01.png!
> !Exception02.png!
> !Exception03.png!
> The exception uploaded the attachment
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
