summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorSimon MacMullen <simon@rabbitmq.com>2013-09-09 11:20:49 +0100
committerSimon MacMullen <simon@rabbitmq.com>2013-09-09 11:20:49 +0100
commitc1b4e6f0eac25349982939a5991f2b32da31f0d8 (patch)
tree7aba866d807a3184c1ba3fda79579a1b6bd3edfc /src
parentcca49430f9c9243800de6bcdca56b22ed915b630 (diff)
downloadrabbitmq-server-git-c1b4e6f0eac25349982939a5991f2b32da31f0d8.tar.gz
Reply with something the channel is going to know how to handle.
Diffstat (limited to 'src')
-rw-r--r--src/rabbit_amqqueue_process.erl6
1 files changed, 5 insertions, 1 deletions
diff --git a/src/rabbit_amqqueue_process.erl b/src/rabbit_amqqueue_process.erl
index 05a149270e..cd56f09884 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",