search

omniti-labs / Net--RabbitMQ

Perl bindings to the librabbitmq-c AMQP library.
Other
25 stars 18 forks source link

basic_return returns no data about the original request #3

Open clintongormley opened 13 years ago

clintongormley commented 13 years ago

Hiya

Would it be possible to add the original message body into the basic return callback arguments?

Because the basic_return callback is only called when the connection is flushed (either by disconnecting or closing a channel), there is no way I can associate the failures with the original message, so although I am aware that there has been a problem, I've lost my message and can't handle failure gracefully.

thanks

clint

postwait commented 13 years ago

I don't believe that information is available. This is an AMQP programming question more than a Net::RabbitMQ one. I'd suggest asking on the rabbitmq-users list how one should correlate a basic.return message with the original message they sent.

On Wed, Jul 6, 2011 at 6:39 AM, clintongormley < reply@reply.github.com>wrote:

Hiya

Would it be possible to add the original message body into the basic return callback arguments?

Because the basic_return callback is only called when the connection is flushed (either by disconnecting or closing a channel), there is no way I can associate the failures with the original message, so although I am aware that there has been a problem, I've lost my message and can't handle failure gracefully.

thanks

clint

Reply to this email directly or view it on GitHub: https://github.com/omniti-labs/Net--RabbitMQ/issues/3

emarcotte commented 12 years ago

For what it is worth, basic.return does not have the information, but when you get basic.return you also get a content header and a content body message on the same channel.