>
> 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 do
Have you tried to look at the RabbitMQ web interface to see what could
be stuck ?
Activating it is quite straightforward, as per Ops Guide :
http://docs.openstack.org/trunk/openstack-ops/content/logging_monitoring.html#rabbitmq
-Sylvain
Le 12/04/2013 17:48, Lowery, Mathew a écrit :
Hi all,
I
2 matches
Mail list logo
