*************** This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on. ***************
What you're seeing is [almost] the correct behaviour. Sending a
mandatory/immediate message to a nonexistent queue (or a queue with no
consumers) is not considered an error, so the commit will succeed. In
this case, the broker will however respond with a basic.return message
informing the client of the lost message.
Unfortunately, I don't think our C client has anyway of handling
basic.returns, so you're out of luck.
The other clients are all capable of handling basic.returns (and
publisher confirms if you're using 2.3.1), so you might want to consider
using one of them. Have a look at this blogpost, it covers what you're
trying to achieve:
http://www.rabbitmq.com/blog/2011/02/10/introducing-publisher-confirms/
Hope this helps.
Cheers,
Alex
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq...@lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq...@lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss