Issues - ask/carrot

ask / carrot

Description:

AMQP Messaging Framework for Python

Sort by: Priority | Votes | Last Updated

Loading…

13.

0 votes

Creating AMQPConnection hangs in busy loop
5 comments Created 4 months ago by azf

Title

Body
When I try to do this straight from the introduction: from carrot.connection import AMQPConnection amqpconn = AMQPConnection(hostname="localhost", port=5672, userid="test", password="test", vhost="test") the whole thing ends up in a busy loop: File "<stdin>", line 1, in <module> File "/Library/Python/2.5/site-packages/carrot-0.5.1-py2.5.egg/carrot/connection.py", line 92, in __init__ self.connect() File "/Library/Python/2.5/site-packages/carrot-0.5.1-py2.5.egg/carrot/connection.py", line 110, in connect connect_timeout=self.connect_timeout) File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/connection.py", line 143, in __init__ File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/connection.py", line 477, in _x_open File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/abstract_channel.py", line 64, in wait File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/connection.py", line 201, in _wait_method File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/method_framing.py", line 212, in read_method File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/method_framing.py", line 127, in _next_method File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/transport.py", line 105, in read_frame File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/transport.py", line 191, in _read It won't time out or anything. Am I doing something wrong or missing something obvious? Tried on OS X 10.5.7, against RabbitMQ 1.6.0 which otherwise seems to be working just fine. This happens both with Python 2.6.2 (from Macports) and Python 2.5.1 (from Apple)
or cancel

When I try to do this straight from the introduction:

from carrot.connection import AMQPConnection
amqpconn = AMQPConnection(hostname="localhost", port=5672, userid="test", password="test", vhost="test")

the whole thing ends up in a busy loop:

File "", line 1, in File "/Library/Python/2.5/site-packages/carrot-0.5.1-py2.5.egg/carrot/connection.py", line 92, in init self.connect() File "/Library/Python/2.5/site-packages/carrot-0.5.1-py2.5.egg/carrot/connection.py", line 110, in connect connect_timeout=self.connect_timeout) File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/connection.py", line 143, in init File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/connection.py", line 477, in x_open File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/abstract_channel.py", line 64, in wait File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/connection.py", line 201, in wait_method File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/method_framing.py", line 212, in read_method File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/method_framing.py", line 127, in next_method File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/transport.py", line 105, in read_frame File "build/bdist.macosx-10.5-i386/egg/amqplib/client_0_8/transport.py", line 191, in read

It won't time out or anything. Am I doing something wrong or missing something obvious?

Tried on OS X 10.5.7, against RabbitMQ 1.6.0 which otherwise seems to be working just fine. This happens both with Python 2.6.2 (from Macports) and Python 2.5.1 (from Apple)

Comments

ask Wed Jul 29 13:11:23 -0700 2009 | link

This is believed to be a problem with amqplib. It usually happens when it can't connect, or authenticate to the server. See: http://github.com/ask/celery/issues#issue/9

Comment
This is believed to be a problem with amqplib. It usually happens when it can't connect, or authenticate to the server. See: http://github.com/ask/celery/issues#issue/9
or cancel

ask Wed Jul 29 13:11:55 -0700 2009 | link

I'm keeping the issue open until we can find a solution, either for carrot or for amqplib.

Comment
I'm keeping the issue open until we can find a solution, either for carrot or for amqplib.
or cancel

chrismiles Thu Jul 30 02:57:36 -0700 2009 | link

I got the same problem on OS X 10.5.7. It happened when the client failed authentication and also when authentication succeeded but the user didn't have permissions to access the vhost.

Comment
I got the same problem on OS X 10.5.7. It happened when the client failed authentication and also when authentication succeeded but the user didn't have permissions to access the vhost.
or cancel

ask Wed Aug 26 01:37:56 -0700 2009 | link

It seems this is actually a RabbitMQ issue that will be fixed in 1.7

Comment
It seems this is actually a RabbitMQ issue that will be fixed in 1.7
or cancel

azf Wed Aug 26 01:42:05 -0700 2009 | link

Good to know. Thank you for the heads-up.

Comment
Good to know. Thank you for the heads-up.
or cancel

Parsed with GitHub Flavored Markdown
16.

1 vote

No exception raised when mandatory=True and message cannot be routed
1 comment Created 2 months ago by ltucker

Title

Body
The documentation for the mandatory parameter of publisher.send states: "If set, the message has mandatory routing. By default the message is silently dropped by the server if it can’t be routed to a queue. However - If the message is mandatory, an exception will be raised instead." At least for the pyamqplib backend, no exception appears to be raised when the message cannot be routed to a queue. This is possibly more of an issue with an underlying driver or a documentation bug.
or cancel

The documentation for the mandatory parameter of publisher.send states:

"If set, the message has mandatory routing. By default the message is silently dropped by the server if it can’t be routed to a queue. However - If the message is mandatory, an exception will be raised instead."

At least for the pyamqplib backend, no exception appears to be raised when the message cannot be routed to a queue. This is possibly more of an issue with an underlying driver or a documentation bug.

Comments

ask Wed Sep 23 03:18:17 -0700 2009 | link

This is actually a combination of several things, first this discussion: http://www.nabble.com/Channel-Cost-td21678526.html shows that in amqplib you have to close the channel to receive the error, so this is definitely a bug. But while testing I could only get it to raise an error if the exchange is not declared, no queues being bound to it didn't seem to affect the outcome. I'm investigating if this is a documentation bug in amqplib or if it's something else. Good catch!

Comment
This is actually a combination of several things, first this discussion: http://www.nabble.com/Channel-Cost-td21678526.html shows that in amqplib you have to close the channel to receive the error, so this is definitely a bug. But while testing I could only get it to raise an error if the **exchange** is not declared, no queues being bound to it didn't seem to affect the outcome. I'm investigating if this is a documentation bug in amqplib or if it's something else. Good catch!
or cancel

Parsed with GitHub Flavored Markdown

Labels

▾
Bug
▾
Feature Request
▾
TODO

Creating AMQPConnection hangs in busy loop

Comments

No exception raised when mandatory=True and message cannot be routed

Comments