diff options
author | Simon MacMullen <simon@rabbitmq.com> | 2014-07-22 13:45:01 +0100 |
---|---|---|
committer | Simon MacMullen <simon@rabbitmq.com> | 2014-07-22 13:45:01 +0100 |
commit | 8987607207335a56daa3bd022d5c0b68452f1f04 (patch) | |
tree | 8765d6aaffc2e4cb25794d91b4c1553c4ab93890 | |
parent | 0d53507cdf5dedcad354e82355618052613588b0 (diff) | |
download | rabbitmq-server-bug26293.tar.gz |
Actually, hold on to confirms when pausing. It's not inconceivable that we might get a false positive from pause_minority_guard, in which case we don't want to throw data away.bug26293
-rw-r--r-- | src/rabbit_channel.erl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/rabbit_channel.erl b/src/rabbit_channel.erl index 27a7d208..043ec7e3 100644 --- a/src/rabbit_channel.erl +++ b/src/rabbit_channel.erl @@ -1574,7 +1574,7 @@ send_confirms(State = #ch{tx = none, confirmed = C}) -> [MsgSeqNo | MSNs] end, [], lists:append(C)), send_confirms(MsgSeqNos, State#ch{confirmed = []}); - pausing -> State#ch{confirmed = []} + pausing -> State end; send_confirms(State) -> case rabbit_node_monitor:pause_minority_guard() of |