[rabbitmq-discuss] Channel Cost

Tue Jan 27 19:16:29 GMT 2009

It looks like I can trigger the error by calling a channel.wait() to
pick up any errors that were triggered by the send. Problem is .wait()
is a blocking call and if everything went all right it just hangs up
the program. I'll take this over to the py-amqplib folks.

-J

On Tue, Jan 27, 2009 at 10:19 AM, Jason J. W. Williams
<jasonjwwilliams at gmail.com> wrote:
> Hi Matthias,
>
> Thank you for the insight. My issue was exactly picking up channel
> errors like publishing to an exchange that doesn't exist.
> Unfortunately, py-amqplib doesn't raise the error until you close the
> channel. I'll look at patching py-amqplib.
>
> -J
>
> On 1/27/09, Matthias Radestock <matthias at lshift.net> wrote:
>> Jason,
>>
>> Jason J. W. Williams wrote:
>>> Is it costly in Rabbit to open and close channels frequently?
>>
>> Yes.
>>
>>> The reason I ask is that you can't pickup errors from a basic_publish
>>> in py-ampqlib until you close the channel.
>>
>> What do you mean by "errors"? There are two types of errors that can
>> arise when the server processes a basic.publish command. AMQP errors,
>> such as malformed requests, missing exchange, etc, close the channel or
>> connection automatically. Routing failures of messages with the
>> 'mandatory' or 'immediate' flag are signalled to the client with an
>> asynchronous basic.return command.
>>
>> Are you saying that in py-amqplib there is no way to get hold of the
>> latter until channel closure? If so that would seem to be an omission in
>> the library and I suggest you take that up with the authors.
>>
>>
>> Matthias.
>>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>