[rabbitmq-discuss] RabbitMQ C# client
S. Doug Hunt
sdh at conix.com
Tue Mar 18 17:44:20 GMT 2014
{"The AMQP operation was interrupted: AMQP close-reason, initiated by Peer,
code=404, text=\"NOT_FOUND - no queue 'DupeQ' in vhost '/'\", classId=50,
methodId=10, cause="}
The above exception is encountered by both the QueueDeclarePassive method -
then the following QueueDeclare.
Here's test code:
try
{
channel.QueueDeclarePassive("DupeQ");
}
catch (Exception ex)
{
var errmsg = ex.Message;
dupeQExists = false;
}
if (dupeQExists)
{
channel.QueueDelete("DupeQ");
}
try
{
channel.QueueDeclare("DupeQ", false, false, false,
null);
}
catch (Exception ex)
{
var errmsg = ex.Message;
}
Since the QueueDeclare seems to issue the same message - I'm thinking that
possibly the passive bit is still set from the prior passive call.
S. Douglas Hunt | Software Engineer
Voice (734) 461-1420 | Fax (305) 675-2448
CONIX Systems, Inc
Safeguarding Payments
This message is intended for the use of the individual or entity to which it
is addressed, and may contain information that constitutes a copyright,
patent, trade secret or confidential information of CONIX Systems, Inc., or
is otherwise privileged, confidential, or exempt from disclosure under
applicable law. If the reader of this message is not the intended
recipient, you are hereby notified that the dissemination, distribution, or
copying of this communication is strictly prohibited. If you have received
this communication in error, please notify us immediately by electronic mail
and delete the original message and destroy any hard copies made thereof.
-----Original Message-----
From: Simon MacMullen [mailto:simon at rabbitmq.com]
Sent: Tuesday, March 18, 2014 11:41 AM
To: Discussions about RabbitMQ; S. Doug Hunt
Subject: Re: [rabbitmq-discuss] RabbitMQ C# client
On 18/03/14 15:12, S. Doug Hunt wrote:
> We create a queue when a review operator first opens a unit of work.
> Other operators can open the same unit of work, but obviously we do
> not want to add items to the queue from the database for subsequent
> operators. So the first thing we do is use the
> QueueDeclarePassive(queuename) method in a try-catch.
>
> So for the first operator fails with the error that the queue was not
> found. We then attempt to use the QueueDeclare method to create the
> queue, however it then fails with the same error.
Exactly the same error? What error message are you getting, precisely?
> I suspect that the QueueDeclarePassive method may have set the passive
> bit and the client is not resetting it after failing so that the
> subsequent call also is acting like a passive call.
The passive bit is not stored in the model object; it's a parameter of the
individual calls to QueueDeclare.
Cheers, Simon
--
Simon MacMullen
RabbitMQ, Pivotal
More information about the rabbitmq-discuss
mailing list