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.<br><br>I was testing the effect of "multicasting" a message, when this came up:<br>
<br>>process_info(pid(0,148,0)).<br>[{current_function,{amqp_network_driver,reader_loop,4}},[...]<br>>pid(0,148,0) ! some_bum_message.<br>>process_info(pid(0,148,0)).<br>undefined<br><br>rabbit.log:<br><br>=ERROR REPORT==== 19-Nov-2008::01:55:02 ===<br>
error on TCP connection <0.2162.43> from <a href="http://127.0.0.1:23482">127.0.0.1:23482</a><br>connection_closed_abruptly<br><br>=INFO REPORT==== 19-Nov-2008::01:55:02 ===<br>closing TCP connection <0.2162.43> from <a href="http://127.0.0.1:23482">127.0.0.1:23482</a><br>
<br>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.<br><br>== 19-Nov-2008::02:01:53 == ERROR - <0.42.0><br>Mnesia(foo@bar): ** ERROR ** mnesia_subscr got unexpected info: some_bum_message<br>
<br>This might be a good test for all processes. I am going to incorporate it into my testing somehow.<br><br>Regards,<br>Edwin Fine<br>