[rabbitmq-discuss] Client API error recovery

Matthias Radestock matthias at lshift.net
Sat Apr 11 17:10:44 BST 2009


Lev,

Lev Walkin wrote:

> Let's see if RabbitMQ client library actually notices this hard failure, 
> when no open channels are present:
> 
> 	16> f(), Connection = lib_amqp:start_connection("test-amq").
> 	<0.66.0>
> 	17> erlang:monitor(process, Connection).
> 	#Ref<0.0.0.94>
> 	18> R = fun() -> receive X -> X after 0 -> empty end end. 
> 
> 	#Fun<erl_eval.20.67289768>
> 	19> length(processes()).
> 	35
> 	20> % Killing the broker
> 	20> length(processes()).
> 	33
> 	21> R().
> 	empty
> 	22> is_process_alive(Connection).
> 	true
> 	23>
> 
> Yes, it does! But it does not die "in full".

We did some work on the erlang client's error handling recently - I get 
the same result on the v1_5 branch, but on 'default' the above works 
fine for me, i.e. the final call returns 'false'.


Matthias.




More information about the rabbitmq-discuss mailing list