[rabbitmq-discuss] [BUG] Erlang client network driver crashes if sent unexpected message

[Edwin Fine]

This is for quite an early version of the Erlang client, certainly not the
head, but I wonder if this doesn't still lurk in there somewhere.

I was testing the effect of "multicasting" a message, when this came up:

>process_info(pid(0,148,0)).
[{current_function,{amqp_network_driver,reader_loop,4}},[...]
>pid(0,148,0) ! some_bum_message.
>process_info(pid(0,148,0)).
undefined

rabbit.log:

=ERROR REPORT==== 19-Nov-2008::01:55:02 ===
error on TCP connection <0.2162.43> from 127.0.0.1:23482
connection_closed_abruptly

=INFO REPORT==== 19-Nov-2008::01:55:02 ===
closing TCP connection <0.2162.43> from 127.0.0.1:23482

I would think that all processes need to handle unexpected messages
gracefully, at the very least by ignoring them or reporting an error, e.g.

== 19-Nov-2008::02:01:53 == ERROR -  <0.42.0>
Mnesia(foo at bar): ** ERROR ** mnesia_subscr got unexpected info:
some_bum_message

This might be a good test for all processes. I am going to incorporate it
into my testing somehow.

Regards,
Edwin Fine
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20081119/a4bdf4bc/attachment.htm