basic_return returns no data about the original request

[clintongormley]

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]

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 < [email protected]>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]

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.