[rabbitmq-discuss] Channel Cost
Jason J. W. Williams
jasonjwwilliams at gmail.com
Tue Jan 27 17:19:17 GMT 2009
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.
On 1/27/09, Matthias Radestock <matthias at lshift.net> wrote:
> Jason J. W. Williams wrote:
>> Is it costly in Rabbit to open and close channels frequently?
>> 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.
More information about the rabbitmq-discuss