Cancelling subscriptions does not consume the message

(Queue names fixed based on @micdenny comments)

Maybe I am doing something wrong.

My system works with prefetchcount=1 and I have multiple asynchronous subscriptions for different topics, for example:

var subscription1 = bus.SubscribeAsync(queueName1, OnMessage1, cfg => cfg.WithTopic("topic1"));
var subscription2 = bus.SubscribeAsync(queueName2, OnMessage2, cfg => cfg.WithTopic("topic2"));
var subscription3 = bus.SubscribeAsync(queueName3, OnMessage3, cfg => cfg.WithTopic("topic3"));

then while a message is being processing, I cancel a subscription, for example:

subscription1.ConsumerCancellation.Dispose();

The thread that was processing the subscription finished correctly, so the message has been processed, but if I start a new subscription for that topic, the message is processed again:

var anotherSubscription = bus.SubscribeAsync(queueName1, OnMessage1, cfg => cfg.WithTopic("topic1"));

Do you have an idea about how can I fix it to avoid process the same message twice?

[zidad]

I agree! however in case of a ‘controlled’ cancellation it should be possible to have the option to finish/ACK the messages that have been picked up.

[andresmoschini]

Thanks @micdenny!

Very detailed and useful answer, I will read the links and try to adapt my consumer to be idempotent.