[rabbitmq-discuss] BasicGet ignoring routing key . Exchange is Direct
videlalvaro at gmail.com
Thu Jan 2 20:49:08 GMT 2014
Replies inline as before:
On Thu, Jan 2, 2014 at 7:10 PM, Patrick Long <pat at munkiisoft.com> wrote:
> More info: The management UI added the Message to the right Queue but the
> exchange is not the usual one. It has used "AMQP default" with a
> delivery_mode of 1.
> Does this explain the unexpected dequeuing?
Probably the management UI published the message to the default
exchange, using the queue name as routing key, which is AMQP's way of
saying: "publish directly to a queue". See more here:
> On 2 January 2014 17:56, Patrick Long <pat at munkiisoft.com> wrote:
>> We are using the C# .NET client library.
>> I create a channel like so
>> channel.ExchangeDeclare(workExchangeName, ExchangeType.Direct);
>> Then bind a queue like
>> channel.QueueBind(this.WorkQueueName, workExchangeName,
>> Today I was trying to debug a failing message from a different
>> environment. I took the message's JSON from that server, via the Management
>> UI, and manually created a message on my local machine, again via the
>> Management UI. There was no option to set a specific RoutingKey, it created
>> one for me with the same name as the queue 'WorkQueue'.
>> The local RabbitMQ had a couple of existing messages with a RoutingKey of
>> When I call channel.BasicGet(this.WorkQueueName, false) in a loop it
>> dequeues all three messages even though the channel was created to look at a
>> queue and exchange with the routing key of
>> Any idea why it would be ignoring the RoutingKey?
>> Patrick Long - Munkiisoft Ltd
> Patrick Long - Munkiisoft Ltd
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss