[rabbitmq-discuss] Temp Queues

Alvaro Videla videlalvaro at gmail.com
Sun Oct 23 17:11:58 BST 2011


When you publish to an AMQP exchange it doesn't uses "temp queues". 

An AMQP Exchange will check the bindings it has and then it will route messages to the destinations that match those bindings. So if you want that your messages to go somewhere then you need to have queues bound to the exchange _before_ you publish messages through it.

See http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/1.3/html-single/Messaging_User_Guide/images/producer-consumer.png

So if you have exchanges but you don't have any queues bound to it, then the exchange will act as a black hole for the messages you publish through it.



On Oct 23, 2011, at 6:03 PM, Gil Strauss wrote:

> Hello
> I'm using exchange for pub-sub method and noticed that it uses temp
> queues, hence if a publisher propagates a message before a listener is
> subscribing to it, the latter won't receive that message.
> What I need for my application is to keep published message for a
> period of time and send the to new subscriber even after the message
> was originally published.
> Is it doable without doing it manually programmatically?
> Thanks,
> Gil
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

Sent form my Nokia 1100

More information about the rabbitmq-discuss mailing list