This may be a known and accepted fact, but it was a surprise to me so
thought it was worth a mention on this list.
If you use the transport_url config option (or pass a url directly to
get_transport()), then the amqp connection pooling appears to be
disabled[1]. That means a new connection is created for every request
send as well as for every response.
So I guess rpc_backend is the recommended approach to selecting the
transport at present(?).
[1] I think this is because if a transport url is specified then the url
will always have at least the hosts set, so the AMQPDriverBase will
always have a non-empty map for server_params, which overrides any use
of pooling.
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
