Old messages left in return queue

[LouisDK]

When a client send a message to a microservice, the client needs to identity a queue to be used for the return message.
The clients gets a "unused" queue from QueuePool.Instance.Get();
But the fact that it is unused is determined by the client keeping track of which return queues are used.
If the previous user of the queue never fetched its message from this queue, the queue might still have a message in it.

I solved this problem by purging the queue everytime I get an "unused" queue from QueuePool.Instance.Get() by doing a channel.QueuePurge(queue.Name)

Change Request

Since the assumption is that when a client gets a new return queue from QueuePool.Instance.Get(), that it would be "ready for use", and empty, would it be possible to make this a default behavior (first purging any potential messages from it) inside QueuePool.Instance.Get() before returning the queue to the client?

[daishisystems]

Let's include this as default initialisation behaviour when retrieving a Queue.