Broker pool not working (for airflow scheduler/worker publishing)

[kiros19]

My setup:
Airflow 3.2.1
celery 5.6.3
kombu 5.6.2
Rabbitmq 4.2.3 with Erlang 27.3.4.7
Rabbit quorum/classic queues; airflow below 3.2, 3.1; rabbit below 4. - same behaviour:

(numbers are for screenshots:)

1. I see endless "connection closed unexpectedly" warnings in RabbitMQ logs.
2. Most of those disconnects come from Airflow scheduler process (some come from worker as well)
3. In rabbit webUI' connections tab i only see worker and flower connections. Flower seems to hold pool while scheduler's not

Scheduler is producing task instance messages, and every single message is a separate connection at the moment.

4. Setting pool to 0 forces scheduler to close each connection properly, so that connection churn is still there, but with no warnings.

Is this behaviour a bug and holding pool for tiny publishes is something that's expected to be working? If so, are there any workarounds / work in progress?
Otherwise, if the behaviour is expected, how do I set up celery+broker properly?

Thank you!

[igorlovich]

We have experienced the same behavior #2451 (comment)