diff options
author | Simon MacMullen <simon@rabbitmq.com> | 2013-09-09 11:20:49 +0100 |
---|---|---|
committer | Simon MacMullen <simon@rabbitmq.com> | 2013-09-09 11:20:49 +0100 |
commit | 263a1e5c3a4c24787baa3e006462aa225fbdf5d9 (patch) | |
tree | 7aba866d807a3184c1ba3fda79579a1b6bd3edfc | |
parent | 0dc84f691a24c0fc93a8e1ed9b2c38c018966860 (diff) | |
download | rabbitmq-server-263a1e5c3a4c24787baa3e006462aa225fbdf5d9.tar.gz |
Reply with something the channel is going to know how to handle.
-rw-r--r-- | src/rabbit_amqqueue_process.erl | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/src/rabbit_amqqueue_process.erl b/src/rabbit_amqqueue_process.erl index 05a14927..cd56f098 100644 --- a/src/rabbit_amqqueue_process.erl +++ b/src/rabbit_amqqueue_process.erl @@ -1070,7 +1070,11 @@ handle_call({init, Recover}, From, false -> #q{backing_queue = undefined, backing_queue_state = undefined, q = #amqqueue{name = QName} = Q} = State, - gen_server2:reply(From, not_found), + %% If the connection has died then what we reply is somewhat + %% moot. But it seems reasonable to act as though the queue + %% was declared and then the connection died - we're only a + %% small timing difference away from that case anyway. + gen_server2:reply(From, {new, Q}), case Recover of new -> rabbit_log:warning( "exclusive owner for ~s went away~n", |