[rabbitmq-discuss] RabbitMQ/Erlang Dependency on SSL

[Wilson, Roger]

This is more an observation than a bug or issue.

I managed to build a version of Elang without SSL.  

RabbitMQ worked fine except when I asked it to create a randomly named
temporary queue.  

(In python using amqplib "queue=chan.declare_queue()") (In java using
the java client "queue=chan.queueDeclare()")

This threw an internal error and closed the channel.

Noticing this in the logs....

=ERROR REPORT==== 4-Feb-2009::12:22:03 === connection <0.221.0>
(running), channel 1 - error:
{undef,[{ssl_base64,encode,
 
[<<245,100,205,50,82,140,18,122,97,89,5,240,91,175,45,136>>]},
        {rabbit_misc,string_guid,1},
        {rabbit_misc,binstring_guid,1},
        {rabbit_channel,handle_method,3},
        {rabbit_channel,handle_message,2},
        {buffering_proxy,'-mainloop/4-fun-0-',3},
        {lists,foldl,3},
        {buffering_proxy,mainloop,4}]}

=WARNING REPORT==== 4-Feb-2009::12:22:03 === Non-AMQP exit reason
'{undef,
                          [{ssl_base64,encode,
 
[<<245,100,205,50,82,140,18,122,97,89,5,240,
                                  91,175,45,136>>]},
                           {rabbit_misc,string_guid,1},
                           {rabbit_misc,binstring_guid,1},
                           {rabbit_channel,handle_method,3},
                           {rabbit_channel,handle_message,2},
                           {buffering_proxy,'-mainloop/4-fun-0-',3},
                           {lists,foldl,3},
                           {buffering_proxy,mainloop,4}]}'

=INFO REPORT==== 4-Feb-2009::12:22:03 === closing TCP connection
<0.221.0> from 127.0.0.1:57464

It looked like the ssl library call is missing.  My guess is it uses
some call into SSL to produce the random queue name.

Installing OpenSSL
(http://www.erlang.org/pipermail/erlang-bugs/2006-September/000233.html)
and rebuilding Erlang solved this.

There was no need to rebuild RabbitMQ itself.



----------------------------------------

This message is intended only for the personal and confidential use of

the designated recipient(s) named above.  If you are not the intended

recipient of this message you are hereby notified that any review,

dissemination, distribution or copying of this message is strictly

prohibited.  This communication is for information purposes only and

should not be regarded as an offer to sell or as a solicitation of an

offer to buy any financial product, an official confirmation of any

transaction, or as an official statement of Lehman Brothers.  Email

transmission cannot be guaranteed to be secure or error-free.

Therefore, we do not represent that this information is complete or

accurate and it should not be relied upon as such.  All information is

subject to change without notice.

----------------------------------------




----------------------------------------
This message is intended only for the personal and confidential use of
the designated recipient(s) named above.  If you are not the intended
recipient of this message you are hereby notified that any review,
dissemination, distribution or copying of this message is strictly
prohibited.  This communication is for information purposes only and
should not be regarded as an offer to sell or as a solicitation of an
offer to buy any financial product, an official confirmation of any
transaction, or as an official statement of Lehman Brothers.  Email
transmission cannot be guaranteed to be secure or error-free.
Therefore, we do not represent that this information is complete or
accurate and it should not be relied upon as such.  All information is
subject to change without notice.
----------------------------------------