[rabbitmq-discuss] queue is locked exclusively

[Reddy, Rajesh (GPT EMEA)]

Hi Matthias,

We do use the queuename supplied by client. It is unique as we use the
processid + userid + datetime in it.
I think the error we are getting might be because of the issue you have
mentioned where the connection terminates non-cleanly.

Thanks
Rajesh

-----Original Message-----
From: Matthias Radestock [mailto:matthias at lshift.net] 
Sent: 04 August 2009 12:41
To: Reddy, Rajesh (GPT EMEA)
Cc: rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] queue is locked exclusively


Rajesh,

Reddy, Rajesh (GPT EMEA) wrote:
> there is something going wrong and trying to resubscribe on
> an existing queue.
> I have added some debug info to the log files, so may be I will get
more
> information regarding why is this happening.

Is the client naming the queue or is it getting the server to generate a
name for it?

The reason I am asking is that if you re-use the same queue name then
there is an unavoidable race condition which might trigger the
RESOURCE_LOCKED error. Specifically, if the connection terminates
non-cleanly, e.g. it gets dropped due to a client or network failure,
and you then immediately reconnect, the auto-deletion of resources of
the old connection may not have happened yet.

I reckon it is unlikely you'd run into this, since the auto-deletion
happens quite quickly, but it is a possibility.


Regards,

Matthias.

--------------------------------------------------------------------------
This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
--------------------------------------------------------------------------