Why is the client needs to be serializable? Have you tried suggestion from
this answer
https://stackoverflow.com/questions/61293343/failed-to-unmarshal-discovery-data-for-component-continuous-proc-with-more-than/61318360#61318360
?
Evgenii
вт, 21 апр. 2020 г. в 00:36, AlexBor :
> Hi Denis,
>
>
Hi Denis,
Both servers are looking to the same server.
Here are code samples:
Server:
public class IgniteServerCacheBootstrap {
final static Logger logger =
LoggerFactory.getLogger(IgniteCacheClient.class);
public static void main(String[] args) throws IgniteCheckedException,
Hi,
Is it possible that another server node is running (without MY_CACHE
deployed) and the failing client is connected to it? The exception you see
should happen only if a cache is not created in the cluster.
Share an implementation of the client logic including the continuous query
piece for
Anyone?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi guys!
I'm trying to play with ContinuousQuery in v2.8.0 with the following setup:
one server node + couple of client nodes running in different JVMs on the
same local machine.
I'm trying to execute same ContinuousQuery on both clients in parallel, but
for some reason first one is able to
