<div>decided to assert that the queue exists for now. Got a weird publish issue. I am publishing to a queue that exists and the message isn't turning up. </div><div> </div><div>I confirmed this by looking at "rabbitmqctl.bat list_queues" and also, via the management plugin.</div>
<div> </div><div>Have you seen this before? What's a good way to troubleshoot?</div><div> </div><div>thanks,</div><div>-Steven<br><br></div><div class="gmail_quote">On 31 January 2012 06:25, Steven Taylor <span dir="ltr"><<a href="mailto:taylste@gmail.com">taylste@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"><div>Hi Jerry,</div><div> </div><div>under the .net client, would that come through on the below?</div>
<pre style="background:white;font-family:Consolas"><span style="color:blue">event</span> <span style="color:rgb(43,145,175)">BasicAckEventHandler</span> BasicAcks;
</pre><div>thanks,</div><div>-Steven</div><div class="HOEnZb"><div class="h5"><div> </div><div><br><br></div><div class="gmail_quote">On 31 January 2012 05:49, Jerry Kuch <span dir="ltr"><<a href="mailto:jerryk@vmware.com" target="_blank">jerryk@vmware.com</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">Hi, Steven<br>
<br>
Asserting the queue existence probably may not be heavyweight enough for you<br>
to worry about. That said, you could consider setting the 'mandatory' flag<br>
when you publish, in which case you'll get an asynchronous notification if the<br>
message cannot be routed to any queue (e.g. if no queues are bound to the<br>
exchange you published too, or your routing key didn't match one that was, etc.)<br>
<br>
Best regards,<br>
Jerry<br>
<div><div><br>
<br>
----- Original Message -----<br>
From: "Steven Taylor" <<a href="mailto:taylste@gmail.com" target="_blank">taylste@gmail.com</a>><br>
To: <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
Sent: Monday, January 30, 2012 9:21:46 PM<br>
Subject: [rabbitmq-discuss] queue discovery<br>
<br>
<br>
<br>
Hi,<br>
<br>
chicken and egg situation here.<br>
<br>
Sender expects that receiver will have created a queue, only, the sender is in this case the first to exist, and so sends a message to a non-existant queue.<br>
<br>
Result: rabbit throws away the message. Is the only way forward to always assert queue existance, or is there a lighter weight alternative? i.e. it'd be nice to get a status or exception back stating if the message got routed or not.<br>
<br>
Same situation could occur if queue is defined with non durable and autodelete. i.e. rabbit goes down and then comes back up.<br>
<br>
thanks,<br>
-Steven<br>
</div></div>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br>
</div></div></blockquote></div><br>