Streaming subscription causes all active streaming subscriptions to retry and disconnect with RabbitMQ (Exception 504)

[KsanGM]

Expected Behavior

When restarting some dynamic streaming subscriptions, only those subscriptions should reconnect without affecting the existing active streaming subscriptions. Existing connections to RabbitMQ queues should remain stable without interruption.

Actual Behavior

When stopping and starting some streaming subscriptions, all existing active streaming subscriptions lose their RabbitMQ connection simultaneously, throwing an exception:

Exception (504) Reason: "channel/connection is not open"

This causes disruptions in unrelated queues and subscription streams.

Steps to Reproduce the Problem

1. Start an application with N dynamic streaming subscriptions (e.g. topic.one, topic.two, topic.three), all consuming messages correctly.
2. Stop M of the subscriptions (e.g. topic.three).
3. Confirm the sidecar logs show clean unsubscribe messages; the other queues still have active consumers.
4. Wait for a duration (e.g. 2 minutes).
5. start the stopped streaming subscriptions (topic.three).
6. Observe that all other active subscriptions lose their RabbitMQ channels and dapr sidecar logs show retries for all queues simultaneously.
7. Observed RabbitMQ logs:
   2026-03-24 12:30:28.706120+00:00 [error] <0.3449.0> operation basic.consume caused a connection exception not_allowed: "attempt to reuse consumer tag 'topic.three'"

Release Note

FIX Streaming subscriptions should not interrupt existing active streams when some subscriptions are stopped and started.