Why do flows stop receiving message un-notified?

Jordi

Hi,

we implemented a Solace consumer using the .NET API following the guidelines (https://tutorials.solace.dev/dotnet/persistence-with-queues/).

We use one session for several flows on distinct queues, respectively.

Sometimes, one of these flows stops receiving messages even though there are still messages in the queue, whereas the other flows are still getting messages.

Restarting the session/flow fixes this, but the problem is that we do not get an exception/error or notification that the flow stopped or went asleep somehow. Are there any intrinsic timeouts we are not aware of or what might be the problem here?

Jordi

Apparantly, it was in fact the session that was disconnected not a single flow on a session.

Sorry for the confusion. I would have deleted this question, but could not find a way how to do this.

marc

No worries @Jordi . thanks for following up with your findings. We'll leave the post here in case others run into the same issue. It's a good reminder to check and see if the session itself is still up.