Durable subscription not receiving more messages about stan.net HOT 5 CLOSED

Would you be able to run the streaming server with the debug (-SD) parameter and provide the output?

CC @kozlovic

from stan.net.

I think I have the same issue too. When I use a simple console app with simple example everything seems ok but on my actual code with the same configurations it's somehow erratic when durable name is set. I went through the STAN's client code and saw that it doesn't get any callback from internal nats connection's subscription:

inboxSub = sc.NATSConnection.SubscribeAsync(inbox, sc.processMsg);

internal void processMsg(object sender, MsgHandlerEventArgs args)
{
bool isClosed = false;
AsyncSubscription sub = null;
Msg raw = null;

        MsgProto mp = new MsgProto();
        ProtocolSerializer.unmarshal(args.Message.Data, mp);

        raw = args.Message;

        lock (mu)
        {
            isClosed = (nc == null);
            subMap.TryGetValue(raw.Subject, out sub);
        }

        if (isClosed || sub == null)
            return;

        sub.processMsg(mp);
    }

It seems that some delay or time dependent issue is causing this.

from stan.net.

I have not experienced this anymore, and I am almost convinced now that what I was experiencing was not caused by anything related to the platform. My particular case involve durable queue groups and after some time I realized that I was using the same subject+queue for my local testing than the instances of the application running in our development environment, so my guess is that most probably all the other messages were being delivered to the other instances running in the development environment.

from stan.net.

So I guess that's not the same issue. Thanks for clarifying this.

from stan.net.

I'm closing this for now, please re-open if this remains an issue.

from stan.net.