Tags: rabbitmq/rabbitmq-server
Tags
Fix channel reuse bug This commit fixes the following test flake that occurred in CI: ``` make -C deps/rabbit ct-amqp_dotnet t=cluster_size_1:redelivery ``` After receiving the end frame, the server session proc replies with the end frame. Usually when the test case succeeds, the server connection process receives a DOWN for the session proc and untracks its channel number such that a subsequent begin frame for the same channel number will create a new session proc in the server. In the flake however, the client receives the end, and pipelines new begin, attach, and flow frames. These frames are received in the server connection's mailbox before the monitor for the old session proc fires. That's why these new frames are sent to the old session proc causing the test case to fail. This reveals a bug in the server. This commit fixes this bug similarly as done in the AMQP 0.9.1 channel in https://github.com/rabbitmq/rabbitmq-server/blob/94b4a6aafdfac6b6cae102f50b188e5ea4a32c0e/deps/rabbit/src/rabbit_channel.erl#L1146-L1155 Channel reuse by the client is valid and actually common, e.g. if channel-max is 0. (cherry picked from commit 6413d2d)
PreviousNext