We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When running the test suite, there are a lot of these warnings in RabbitMQ logs:
2024-03-07 01:36:09.548679+00:00 [warning] <0.1347.0> closing AMQP connection <0.1347.0> (172.17.0.1:54740 -> 172.17.0.2:5672, vhost: '/', user: 'guest'): 2024-03-07 01:36:09.548679+00:00 [warning] <0.1347.0> client unexpectedly closed TCP connection 2024-03-07 01:36:09.549107+00:00 [warning] <0.1334.0> closing AMQP connection <0.1334.0> (172.17.0.1:54730 -> 172.17.0.2:5672, vhost: '/', user: 'guest'): 2024-03-07 01:36:09.549107+00:00 [warning] <0.1334.0> client unexpectedly closed TCP connection 2024-03-07 01:36:09.549143+00:00 [warning] <0.1321.0> closing AMQP connection <0.1321.0> (172.17.0.1:54714 -> 172.17.0.2:5672, vhost: '/', user: 'guest'): 2024-03-07 01:36:09.549143+00:00 [warning] <0.1321.0> client unexpectedly closed TCP connection 2024-03-07 01:36:09.549494+00:00 [warning] <0.1308.0> closing AMQP connection <0.1308.0> (172.17.0.1:54710 -> 172.17.0.2:5672, vhost: '/', user: 'guest'): 2024-03-07 01:36:09.549494+00:00 [warning] <0.1308.0> client unexpectedly closed TCP connection [...]
The text was updated successfully, but these errors were encountered:
sajith
No branches or pull requests
When running the test suite, there are a lot of these warnings in RabbitMQ logs:
The text was updated successfully, but these errors were encountered: