a bug in erlang node after an error at another node

Question

i created 2 erlang nodes in the same Windows machine with two cmd windows:\'unclient@MYPC\' and \'unserveur@MYPC\' , the server code is very simple :

-module(ser         


        

Answer 1

This happens because the EXIT message is sent to any process that is linked to the server process, which is not necessarily the same process that sent the message.

It works when you run it in the shell, since the shell process gets linked to the server process, and the shell process is also the one that calls the inverse function. However, when you make an RPC call, the inverse function is called from a different process.

Try making the RPC call from the client, and then running flush(). in the shell of the server node, and you should see the EXIT message.