Option to turn off channel sharing, or a way for it to not share a channel when confirm_select is enabled

[TDola]

I am setting up the proxy, when upgrading to version 2, it locks up connections.
My best guess, is it's lumping 130 connections and channels together. But some of them have publisher confirms and some do not. When one of those publishes, it changes a shared channel, breaking anyone else using it.

That's my best theory anyways. The problem of it hanging with no errors seems to resolve when I roll back to proxy v1.0.0.

If it matters, we are using PhpAmqpLib with channel->confirm_select() and handlers for channel->set_ack_handler() channel->set_nack_handler() set. Connections come from 100s of different sources and scripts all going through the 1 proxy.

[spuun]

Since v2.0.0 no channels are shared, so the problem shouldn't be related to publisher confirms.

Everything just stops? Does amqproxy accept new connections?

Nothing of interests logged by amqproxy?

[TDola]

Yeah it just stops, it keeps accepting connections, but publisher confirms just stop working and stop getting confirmations. Nothing at all in the logs, even in debug mode in the docker container.

[spuun]

So you have ~130 connections, each opening one channel? And some will use publishers confirms? Are all channels publishing? Do you have consumers among these?

Are all connections using the same credentials?

[TDola]

So you have ~130 connections, each opening one channel?

Yes, sometimes more.

And some will use publishers confirms?

Yes, messages coming from a apache PHP REST server use publisher confirms.

Are all channels publishing? Do you have consumers among these?

Yes some are publishing. The publishing ones are usually short lived, the consumers stay running, usually for up to 6 hours. The consumers are also in PHP.

Are all connections using the same credentials?

Yes all the same credentials. Would separating them solve the problem?

[spuun]

Yes all the same credentials. Would separating them solve the problem?

I don't think so, but it give me that all clients connections will be proxied through the same upstream connection (well, may be a couple depending on max channels).

Anyhow, maybe that I have reproduce this. At least I seem to have hit some kind of deadlock.

[spuun]

What amqp broker are you using?

[TDola]

RabbitMQ 3.13.7
Erlang 26.2.4
Hosted by cloudamqp