[rabbitmq-discuss] AMQP URIs do not support connection_timeout?
Simon MacMullen
simon at rabbitmq.com
Tue Sep 24 16:56:44 BST 2013
Hmm. This is currently rather badly documented, it's split between the
URI page and the shovel page (those query string params were originally
shovel-specific).
I'll file a bug to get this made clearer...
Cheers, Simon
On 24/09/13 16:50, Steve Powell wrote:
> The AMQP URI spec page doesn't explain how to specify these parameters in the URI.
> Should they be documented there? The Java Client (as far as I know) doesn't look
> for them when interpreting an URI.
>
> Steve Powell [Cell: +44-7815-838-558] [RabbitMQ, Pivotal]
> “L’enfer, c’est les autres.” Sartre
>
> On 23 Sep 2013, at 16:03, Simon MacMullen <simon at rabbitmq.com> wrote:
>
>> On 23/09/13 15:59, Fred Dushin wrote:
>>> Hi folks,
>>>
>>> I was wondering why we don't support the connection_timeout
>>> amqp_params_network parameter in the amqp_uri:parse functions.
>>
>> Probably an oversight, good point. Will fix...
>>
>> Cheers, Simon
>>
>> --
>> Simon MacMullen
>> RabbitMQ, Pivotal
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
--
Simon MacMullen
RabbitMQ, Pivotal
More information about the rabbitmq-discuss
mailing list