Delegate generic EXIT handling to implementation modules

The catch-all-and-ignore clause resulted in connections not actually
dying when they were expected to, wrecking havoc to some RabbitMQ server
test suites.

Per discussion with @dcorbacho.

This amends #79.

deps/amqp_client/src/amqp_direct_connection.erl

@@ -78,6 +78,8 @@ handle_message({'DOWN', _MRef, process, _ConnSup, shutdown}, State) ->
     {stop, {shutdown, node_down}, State};
 handle_message({'DOWN', _MRef, process, _ConnSup, Reason}, State) ->
     {stop, {remote_node_down, Reason}, State};
+handle_message({'EXIT', Pid, Reason}, State) ->
+    {stop, rabbit_misc:format("stopping because dependent process ~p died: ~p", [Pid, Reason]), State};
 handle_message(Msg, State) ->
     {stop, {unexpected_msg, Msg}, State}.
 

deps/amqp_client/src/amqp_gen_connection.erl

@@ -230,8 +230,9 @@ handle_info({'EXIT', BlockHandler, Reason},
               "Reason: ~p~n", [self(), BlockHandler, Reason]),
     erlang:demonitor(Ref, [flush]),
     {noreply, State#state{block_handler = none}};
-handle_info({'EXIT', _Pid, _Reason}, State) ->
-    {noreply, State};
+%% propagate the exit to the module that will stop with a sensible reason logged
+handle_info({'EXIT', _Pid, _Reason} = Info, State) ->
+    callback(handle_message, [Info], State);
 handle_info(Info, State) ->
     callback(handle_message, [Info], State).
 

deps/amqp_client/src/amqp_network_connection.erl

@@ -73,6 +73,8 @@ handle_message(heartbeat_timeout, State) ->
     {stop, heartbeat_timeout, State};
 handle_message(closing_timeout, State = #state{closing_reason = Reason}) ->
     {stop, Reason, State};
+handle_message({'EXIT', Pid, Reason}, State) ->
+    {stop, rabbit_misc:format("stopping because dependent process ~p died: ~p", [Pid, Reason]), State};
 %% see http://erlang.org/pipermail/erlang-bugs/2012-June/002933.html
 handle_message({Ref, {error, Reason}},
                State = #state{waiting_socket_close = Waiting,