Nats Request/Reply works in Debug but error when run standalone

[alberk8]

I have a Nats Request/Reply in two apps. On the Reply app on VS debug there is no issue but when I compile and run it in CLI (myapp.exe)

I am getting the error below after the first Request/Reply call. What could be the issue?

Subscription GCd but was never disposed

Another message that I see is sometimes on Request/Reply is End subscription MaxMsgs. What does this mean?

[mtmk]

we have some protection against subscriptions that are not properly disposed which involves weak refs / GC etc. Can you post a Program.cs (ideally, or some code) demonstrating the issue?

[mtmk]

@AngeloBestetti I'm not convinced running GC.Collect() is helping here. Did you have any progress on this?

[AngeloBestetti]

I wrote in go and works fine now

[mtmk]

glad you solved the issue. sad to see you go (no pun intended). let us know if you decide to use C# again.

[AngeloBestetti]

@mtmk Ziya, found something strange, when I use just reply msg works and does not lost the "subscription", what is happening is my entity framework, before I reply, I need to query a DB to get some info. If I remove this part there is no error. If I put back after few seconds I got the Message.

Does EF Core interfere with NATS?

ClienteModel cliente = await Utils.GetCliente(req.Credenciais.Email, req.Credenciais.Senha); <------ This is the Problem, if I remove no errors resposta = await Utils.GetPessoaFisicaNFe(req); await msg.ReplyAsync(resposta); Console.WriteLine($"Nome: {JsonConvert.SerializeObject(resposta)}");

[mtmk]

thanks @AngeloBestetti. this is interesting! I think it might be to do with await creating the state machine code behind the scenes. @caleblloyd has a fix in #506. have a look at Kevin Gosse's post he's mentioned. I think that blog post might explain the behaviour you're seeing above.

• Keep sub alive when reading channel #506

[darkwatchuk]

I've previously found if you don't await / pin a long running task then it gets GC'd

[mtmk]

@darkwatchuk fyi, I thought Kevin Gosse's post @caleblloyd found (see #506) was quite interesting: https://minidump.net/c-using-gc-keepalive-in-async-methods-8d20fd79f0a0/

[mtmk]

Hi @AngeloBestetti, we have a new release that should fix the issue you mentioned above. Please give it a go and let us know if it fixes the issue for you, cheers: https://github.com/nats-io/nats.net.v2/releases/tag/v2.2.3

[mtmk]

Hi @alberk8 https://github.com/nats-io/nats.net.v2/releases/tag/v2.2.3 should fix this issue

[AngeloBestetti]

@mtmk Great, I just deployed and tested, WORKS fine, let´s run for few hours. Thank you

[AngeloBestetti]

Working perfect now, thank you Ziya

[alberk8]

After a few days, still running.

[mtmk]

All credits to @caleblloyd for the fix #506. Thank you 🙏