Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ResourceLocked: Queue.declare: (405) RESOURCE_LOCKED - cannot obtain exclusive access to locked queue 'rpc.reply-standalone_rpc_proxy' ...

See original GitHub issue

We’re having on-and-off connectivity issues with RabbitMQ & nameko and occasionally we’re seeing a ResourceLocked error bubbling up from inside kombu.

>>> n.rpc.browser_session_service.create()
^CTraceback (most recent call last):
  File "<console>", line 1, in <module>
  File "/venv/local/lib/python2.7/site-packages/nameko/rpc.py", line 352, in __call__
    return reply.result()
  File "/venv/local/lib/python2.7/site-packages/nameko/rpc.py", line 333, in result
    self.resp_body = self.reply_event.wait()
  File "/venv/local/lib/python2.7/site-packages/nameko/standalone/rpc.py", line 57, in wait
    self.queue_consumer.get_message(self.correlation_id)
  File "/venv/local/lib/python2.7/site-packages/nameko/standalone/rpc.py", line 163, in get_message
    self._setup_consumer()
  File "/venv/local/lib/python2.7/site-packages/nameko/standalone/rpc.py", line 93, in _setup_consumer
    maybe_declare(self.queue, channel)
  File "/venv/local/lib/python2.7/site-packages/kombu/common.py", line 113, in maybe_declare
    return _maybe_declare(entity, declared, ident, channel)
  File "/venv/local/lib/python2.7/site-packages/kombu/common.py", line 120, in _maybe_declare
    entity.declare()
  File "/venv/local/lib/python2.7/site-packages/kombu/entity.py", line 522, in declare
    self.queue_declare(nowait, passive=False)
  File "/venv/local/lib/python2.7/site-packages/kombu/entity.py", line 548, in queue_declare
    nowait=nowait)
  File "/venv/local/lib/python2.7/site-packages/amqp/channel.py", line 1259, in queue_declare
    (50, 11),  # Channel.queue_declare_ok
  File "/venv/local/lib/python2.7/site-packages/amqp/abstract_channel.py", line 69, in wait
    return self.dispatch_method(method_sig, args, content)
  File "/venv/local/lib/python2.7/site-packages/amqp/abstract_channel.py", line 87, in dispatch_method
    return amqp_method(self, args)
  File "/venv/local/lib/python2.7/site-packages/amqp/channel.py", line 243, in _close
    reply_code, reply_text, (class_id, method_id), ChannelError,
ResourceLocked: Queue.declare: (405) RESOURCE_LOCKED - cannot obtain exclusive access to locked queue 'rpc.reply-standalone_rpc_proxy-2e64ba30-447e-413e-a2d6-57e5db87fed5' in vhost 'staging-rpc-rabbitmq'

Has anyone seen anything like this?

Issue Analytics

State:
Created 7 years ago
Comments:13 (9 by maintainers)

Top GitHub Comments

7reactions

mattbennettcommented, Dec 18, 2017

I intend to pick this up over the Christmas break or shortly thereafter

4reactions

rolandobloomcommented, Nov 7, 2017

Any updates on this issue?

Top Results From Across the Web

Queue.declare: (405) RESOURCE_LOCKED - cannot obtain ...

ResourceLocked : Queue.declare: (405) RESOURCE_LOCKED - cannot obtain exclusive access to locked queue 'st2.trigger.watch.St2Timer-883eb620b9' in vhost '/' # ...

Cannot obtain exclusive access to locked queue

So the client can't declare the queue and it can't receive the messages from the AMQP server. It happens after this message: =WARNING...

cannot obtain exclusive access to locked ... - Google Groups

It appears that there is a race condition - the Rabbit Admin failed to redeclare the anonymous, auto-delete, exclusive queue because the old...

[Contrail] 1909 - cannot obtain exclusive access to locked queue

[Contrail] 1909 - channel error: 405: AMQP_QUEUE_DELETE_METHOD caused: RESOURCE_LOCKED - cannot obtain exclusive access to locked queue.

Error AMQP 405 - RESOURCE_LOCKED - OutSystems

Error executing PubSub jobs, 89 consecutive Jobs failed. Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by ...