That's the problem, after the call to cache ("my-cache") it just holds,
which is quite odd, because the call to get all cache names works normally,
but attempting to get the instance fails.
I can see from the topology that it connects to the correct cluster.
Thanks
On 9 Nov 2017 11:55 p.m., "Evgenii Zhuravlev" <e.zhuravlev...@gmail.com>
wrote:
> Hey,
>
> Which exception threw there? Could you share stacktrace?
>
> Does here really client reconnects to the same cluster, or it was after
> the server node was restarted?
>
> Evgenii
>
>
> 2017-11-09 18:34 GMT+03:00 guillMelo <guilhe...@gmelo.org>:
>
>> Hello,
>> I am sorry If I am not being clear, my goal is that, once the client
>> cannot
>> reconect to the cluster as the EVT_CLIENT_NODE_RECONNECTED event is
>> triggered, I want to get a IgniteCache instance so I can re-register a
>> continuous query. however, after the event is trigger if I do a
>> ignite.cache("cachename") It just fails silently.
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>
>
