Currently for each connector a new subscriber for Notification 2.0 is created. When the connector is removed the connection is just shut down but the subscriber is not unsubscribed leading to building endless queues on the server.
Proposed fix: On connector removal also unsubscribe the according subscriber.
switschel
commented
1 month ago
Currently for each connector a new subscriber for Notification 2.0 is created. When the connector is removed the connection is just shut down but the subscriber is not unsubscribed leading to building endless queues on the server.
Proposed fix: On connector removal also unsubscribe the according subscriber.