Re: Asp.net client reconnect problem

Yes, this fix will be included in upcoming Ignite 2.0. You can also download recent nightly build of NuGet package: https://cwiki.apache.org/confluence/display/IGNITE/Nightly+Builds On Fri, Apr 7, 2017 at 2:43 PM, ozgurnevres wrote: > I think you mean the source code on github, did I get it rig

Re: Asp.net client reconnect problem

I think you mean the source code on github, did I get it right? Will this fix be included in the future updates of the Ignite nuget package? thanks -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11808.html Sent from the

Re: Asp.net client reconnect problem

Seems it related with https://issues.apache.org/jira/browse/IGNITE-4473 issue. This fixed in master you can try to build ignite from master and check. On Thu, Apr 6, 2017 at 3:51 PM, Alper Tekinalp wrote: > Hi. > > All segmentation issues that I encountered were due to long GC pauses. > Maybe th

Re: Asp.net client reconnect problem

Hi. All segmentation issues that I encountered were due to long GC pauses. Maybe that can be a clue. Regards. On Thu, Apr 6, 2017 at 3:40 PM, Pavel Tupitsyn wrote: > Igniters, there is a node segmentation in the log, can someone with > experience in this area step in? > This is not related to

Re: Asp.net client reconnect problem

Igniters, there is a node segmentation in the log, can someone with experience in this area step in? This is not related to ASP.NET and .NET, I believe. On Thu, Apr 6, 2017 at 1:45 PM, ozgurnevres wrote: > Any suggestion? :( > > > > -- > View this message in context: http://apache-ignite-users.

Re: Asp.net client reconnect problem

Any suggestion? :( -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11772.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Asp.net client reconnect problem

log.txt Hi Pavel, The log file (after ClientReconnected is fired while server is still down) is attached. thanks -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asp-net-client-reconnect-prob

Re: Asp.net client reconnect problem

And yes, I am sure there's no other server node. (Topology shows 1 server ven I restart the server) -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11751.html Sent from the Apache Ignite Users mailing list archive at Nabbl

Re: Asp.net client reconnect problem

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

Re: Asp.net client reconnect problem

> Grid is in invalid state to perform this operation When does this happen? Can you provide more details or a project to reproduce? Are you sure you don't call Ignition.Stop somewhere? On Wed, Apr 5, 2017 at 2:08 PM, ozgurnevres wrote: > While we send a query to our cluster, We get the followin

Re: Asp.net client reconnect problem

While we send a query to our cluster, We get the following error message from asp.net client node "Grid is in invalid state to perform this operation. It either not started yet or has already being or have stopped [gridName=myGrid1, state=STOPPED]" Then we restart every thing on client node(app p

Re: Asp.net client reconnect problem

> 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

Asp.net client reconnect problem

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 s