TLS "unexpected message"

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
Report Content as Inappropriate

TLS "unexpected message"

Kim Hansen
We're running RabbitMQ 3.6.6 on top of Erlang 19.1.5 and we are seeing these errors in the log:

=ERROR REPORT==== 13-Dec-2016::11:48:04 ===
SSL: {connection,{alert,2,20,{"tls_record.erl",229},undefined}}: ssl_connection.erl:842:Fatal error: unexpected message
=WARNING REPORT==== 13-Dec-2016::11:48:04 ===
STOMP connection -> terminated with reason {inet_error,
                                                                                 "unexpected message"}}, closing it
=ERROR REPORT==== 13-Dec-2016::11:48:04 ===
** Generic server <0.21658.12> terminating
** Last message in was {inet_async,
                           {error,{tls_alert,"unexpected message"}}}
** When Server state == {reader_state,
                         " ->",
                           57788,<<" ->">>,
                             [{<<"product">>,longstr,<<"STOMP client">>}]},
** Reason for termination ==
** {inet_error,{tls_alert,"unexpected message"}}

and it looks like it might cause a memory leak because we also get a lot of these:

=WARNING REPORT==== 13-Dec-2016::11:48:05 ===
STOMP detected missed client heartbeat(s) on connection ->, closing it

We've asked Pivotal about the root cause of this and they tell us that it is a TLS alert (from Erlang) that ceases all TCP traffic.

I'd like to know if we can provide you with more information about this? tcpdump traces or the like? If yes, can you provide us with a tcpdump command that include a pseudo source IP address or something and we are more than happy to dig into this and provide some logs.


erlang-bugs mailing list
[hidden email]