<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">The RabbitMQ logs showed no information
during SSL. Unfortunately, I don't control the load balancer and
they were sure it was configured properly, so I had to eliminate
every other possibility.<br>
<br>
Long story short, it was the load balancer. Got somebody to
reconfigure it and now it works.<br>
<br>
On 8/13/2013 2:04 AM, Michael Klishin wrote:<br>
</div>
<blockquote
cite="mid:0B19D27C-F55C-47FC-87DC-49158AE4BCFB@gopivotal.com"
type="cite">
<pre wrap="">Sean Whyte:
</pre>
<blockquote type="cite">
<pre wrap="">When the code gets to 'factory.newConnection()', it always times out. With the same code, if I change the port to 80 (and remove the SSL specific stuff), it works fine. I have tried all the various useSslProtocol methods with their different parameters, but always the same timeout result. Not sure what I'm missing.
</pre>
</blockquote>
<pre wrap="">
It may time out because nothing gets forwarded, take a look at your load balancer logs. Inspecting RabbitMQ
logs should reveal if there are any AMQP 0-9-1 connection negotiation issues. Please post
them here if you see any.
--
MK
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
rabbitmq-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>
<a class="moz-txt-link-freetext" href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a>
</pre>
</blockquote>
<br>
</body>
</html>