[rabbitmq-discuss] Exchange and queue naming conventions

Jerry Kuch jerryk at rbcon.com
Thu Aug 30 23:43:49 BST 2012

You might consider having producers use the mandatory flag.  That way if
it's not possible for Rabbit to put the message into at least one queue,
you'll get it sent back to you via a basic.return and the producer can
rethink its life choices accordingly.

Best regards,

On Thu, Aug 30, 2012 at 6:53 AM, tlempart <tlempart at gmail.com> wrote:

> Hi,
> Your discussion was very helpful for me. In particular, information about
> who is responsible for creating what. However, I see one problem in case of
> two independent applications, where the first one constains producer (PA)
> and the second one contains consumer (CA). At the beginning there are no
> exchanges/queues/bindings on the rabbitmq, so if the PA starts first, than
> the producer creates exchange and starts sending messages. Because consumer
> is not ready (CA has not yet started), than the queue and binding is not
> created and the messages are lost. Is there any simple way/pattern to solve
> such case, I mean to suspend sending messages by producer, until the
> consumer creates own infrastructure (queue and binding)?
> --
> View this message in context:
> http://rabbitmq.1065348.n5.nabble.com/Exchange-and-queue-naming-conventions-tp7254p21702.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120830/04b8fae6/attachment.htm>

More information about the rabbitmq-discuss mailing list