x-mq-results-queue important
Result queue
Directs this message's results to a named queue instead of the node's own.
In detail
The header that makes a shared node workable. Results are consumed destructively, so Hub and a customer's application cannot both read the node's queues — but the customer's mail can name its own queue, and then each side sees its own traffic in full. It is also a small trap: a queue named here that nobody consumes accumulates exactly like the node's own, with the same consequences for the broker.
What happens if you get it wrong
A named queue with no consumer.Unbounded growth, the same as an unread node queue.inference · inference