> > Finally, it appears that when an RPC call times out, the original message, at > least is some cases like 'network.hostname' queue, is left in place to be > consumed when a consumer is available. This seems like an odd design--if I > take corrective action in response to an RPC timeout, I don't think I want > that message processed ever. >
For what it is worth, Grizzly introduces TTLs for individual messages as they're injected into RabbitMQ and Qpid. This was already the behavior for ZeroMQ, in Folsom. Regards, Eric Windisch _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
