In a NoB using Virtual Topics, a problematic scenario shows that after the consumer is removed and the queue is deleted. The deleted queue re-emerges with new messages from a highly active producer (that is never stopped).

The destination in the broker is gone, but the destination in the kahadb index is not (it gets recreated in error), and that message send (that caused the recreation) won't get deleted, holding up gc.