Page MenuHomePhabricator

[Tunnelbroker] close RabbitMQ queue when client disconnects
ClosedPublic

Authored by kamil on Sep 28 2023, 7:42 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 1, 11:10 AM
Unknown Object (File)
Fri, Nov 1, 11:09 AM
Unknown Object (File)
Fri, Nov 1, 11:08 AM
Unknown Object (File)
Fri, Nov 1, 11:08 AM
Unknown Object (File)
Fri, Nov 1, 10:46 AM
Unknown Object (File)
Fri, Nov 1, 6:41 AM
Unknown Object (File)
Tue, Oct 29, 1:07 AM
Unknown Object (File)
Oct 13 2024, 11:31 AM
Subscribers

Details

Summary

This might cause issues and was causing error in past:

  1. We run persistence test
  2. Queue is created, but never closed
  3. We run tests again, messages are in database, but are also put into RabbitMQ
  4. Consumer receives messages, and try to send but socket is closed at this time
  5. It generates error in Tunnelbroker logs

Depends on D9316

Test Plan
  1. Without this changes run:

cd services/commtest && cargo test --test tunnelbroker_persist_tests  -- --nocapture

  1. Wait for the test to finish
  2. Go to RabbitMQ console and it shows queues:

Screenshot 2023-09-28 at 15.28.20.png (236×1 px, 23 KB)

  1. Restart RabbitMQ
  2. Do steps 1, 2, 3 and the console should show 0 queues:

Screenshot 2023-09-28 at 15.40.04.png (248×1 px, 25 KB)

Diff Detail

Repository
rCOMM Comm
Branch
tb-work-2
Lint
No Lint Coverage
Unit
No Test Coverage