ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel Tupitsyn <ptupit...@apache.org>
Subject Re: Asp.net client reconnect problem
Date Wed, 05 Apr 2017 09:59:07 GMT
> a few seconds later fires "ClientReconnected" event
This is suspicious. Are you sure no other nodes are running on your machine
or in the local network?
Can you attach the log?

I have tested this exact scenario today (ASP.NET runs Ignite in client
mode, server is a standalone executable) and it works as expected.

On Wed, Apr 5, 2017 at 12:54 PM, ozgurnevres <ozgur.nevres@gmail.com> wrote:

> Hi,
> I am running Ignite on asp.net as a client node. I have also a server node
> as console application.
> M problem is:
> 1- When I stop the server node when asp.net client node is connected, it
> fires first "ClientDisconnected" event. Then, a few seconds later fires
> "ClientReconnected" event. Why? The server is still down.
> 2- Then I restarting the server node. The client never reconnects again. In
> the server's console screen, the number of clients remains 0.
> Am I missing something? How can I correctly handle the "server temporarily
> down" or "server is restarting" case?
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message