Mapping bindings between a stream and a pub-sub exchange causes publishers to fails and channels on publishers to explode in count

[jefftrimm]

Mapping bindings between a stream and a pub-sub exchange causes publishers to fails and channels on publishers to explode in count.

Step to reproduce:

1. 2-node cluster.
2. Create a pub-sub exchange.
3. Create a regular mirrored queue.
4. Create one or more topic bindings to the queue.
5. Have a publisher with a persistent connection to RabbitMQ publish events
6. Events will be delivered to classic queue with no issues
7. Create a stream queue, in my case I set a max-age of events to 1D, though it's unclear if that matters.
8. Bind the stream queue to the pub-sub exchange with the same topic bindings as the classic queue.
9. Attempt to publish more messages from the publisher which is still connected to the broker.
10. Events will show up in the stream, but the publisher client never seems to successfully publish and the number of channels in the connection will continue to grow until the max channel limit of 2047 channels is reached.

[michaelklishin]

I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :(