Hi, Looks like the Ignite instance gets disposed or stopped. Make sure that you call Ignition.Start() only once and keep the instance alive.
For a lazy initialization, use the following pattern: var ignite = Ignition.TryGetIgnite() ?? Ignition.Start() You can use IIgnite.Stopped event to debug the problem and see where the stop call comes from. On Fri, Feb 26, 2021 at 10:34 AM Eyalkz <[email protected]> wrote: > Hi, > > I was able to create a node with a named memory cache and put/get/compute > work fine. > > However, it only works if I do it all in a single web method. > > If I call another method I created to query the cache again I get an empty > cache. (I call GetOrCreate based on the name and GetCache cannot find it so > I'm pretty sure Ignite just cannot find anything in memory and creates an > empty cache) > > I believe it is creating a separate instance every time instead of reusing > the same instance. > How do I keep the Cache online and populated with data between different > calls to the same service? > > I'm using WCF service for the method call. IIS, Windows Server 2016, .NET > (same code as demo) > I tried the following: > I. Naming the instance but I get the same behavior. > II. Using a static field [Instance Reference] to the Ignition.Start with > Lazy<> loading but no luck. > III. Install Windows Service Ignite.NET but same behavior > > This might be an issue with application pool? Any other suggestions? > > I appreciate your help. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
