Hi, Pavel The steps are below: 1- I am starting server node. 2- Then starting asp.net client node. 3- Querying database. Works perfect. 4- Stopping server node. Ignite fires ClientDisconnected as one expected. 5- A few seconds later, while server is still down, Ignite fires ClientReconnected event (this is confusing, I don't know why). 6- After ClientReconnected fired, I restart the server node. 7- Nothing happens. It never fires ClientReconnected again. 8- When I query database in this situation, I get "Grid is in invalid state to perform this operation. It either not started yet or has already being or have stopped" exception.
I didn't implemented the logging yet, I'll read how to do it and then I'll send you the logs. Thanks -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11750.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
