[rabbitmq-discuss] SSL_TIMEOUT

Dmitry Andrianov dmitry.andrianov at alertme.com
Mon Jun 9 16:21:26 BST 2014

I am reviving a very old thread here....
As your bugtracker is not public - is it somehow possible to submit a 
bug/issue/enhancement there?

I reeeally do not want to run a custom build of RabbitMQ server but 
there seem to be no other way to change SSL_TIMEOUT.
The problem is - we cannot control network environment where client apps 
are started and if in that environment DNS lookup takes more then 5 
seconds - the connection just fails and there is nothing can be done 
about it.

Any of the following would help:
* configurable SSL_TIMEOUT on the server side
* somehow modify SSL layer in Java client so it does not try to reverse 
lookup IP address into a name. I had a very quick look and I doubt that 
is easy because it is not RabbitMQ client but the Java standard library 


On 18/09/13 11:34, Matthias Radestock wrote:
> On 18/09/13 11:30, Dmitry Andrianov wrote:
>> we cannot make 200Mhz CPU run any faster.
> Understood. Though 5 seconds is still a long time even on a 200MHz CPU.
> Think how many instructions get executed in that time :)
> Matthias.

This email is for the use of the intended recipient(s) only.
If you have received this email in error, please notify the sender immediately and then delete it.
If you are not the intended recipient, you must not use, disclose or distribute this email without the
author's prior permission. AlertMe.com Ltd. is not responsible for any personal views expressed
in this message or any attachments that are those of the individual sender.

AlertMe.com Ltd, 30 Station Road, Cambridge, CB1 2RE, UK.
Registered in England, Company number 578 2908, VAT registration number GB 895 9914 42.

More information about the rabbitmq-discuss mailing list