[ 
https://issues.apache.org/jira/browse/IGNITE-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663270#comment-15663270
 ] 

ASF GitHub Bot commented on IGNITE-4117:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/1195


> .NET: after the reconnection client fails while trying to get a reference to 
> a cache
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-4117
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4117
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Denis Magda
>             Fix For: 1.8
>
>
> In the following example 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/ClientReconnectExample.cs
> we deliberately added these lines of the code
> {code}
>                             while (!task.IsCompleted) // workaround.
>                                 task.Wait();
>                             Console.WriteLine(">>> Client has reconnected 
> successfully");
>                             //Workaround.
>                             System.Threading.Thread.Sleep(3000);
> {code}
> because otherwise after the clients successfully reconnects to the cluster it 
> expects different issues that prevent from using it. In particular, the 
> example will throw cache related exception at the next line but this mustn't 
> happen
> {code}
>                             // Updating the reference to the cache. The 
> client reconnected to the new cluster.
>                             cache = ignite.GetOrCreateCache<int, 
> string>(CacheName);
> {code} 
> Step to reproduce:
> - Start remote .NET node;
> - Start the example;
> - Restart the remote node.
> The issue is 100% reproducible on my VirtualBox Windows 8.1 machine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to