Make it easier to detect blocked connections
jjank opened this issue · 0 comments
jjank commented
Is your feature request related to a problem? Please describe.
TL;DR: Detecting blocked connections can be quite tricky when you don't have access to the broker
- In the project I'm currently on we are using the
rabbitmq-jmsclient (not my choice but we cannot change this in the forseeable future) - For reasons beyond our control the RabbitMQ broker blocked our clients again and again (Ops is working to resolve this properly)
- We found it quite hard to get to the bottom of this, specifically:
- We found no (supported?) way to add a
BlockedListenerusing therabbitmq-jmsapis (as far as I remember access tocom.rabbitmq.client.Connectionis hidden behind theConnectionFactorybut that's a deliberate decision I suppose and a different discussion) - To the best of our research no default (e.g. logging) happens upon blocking
MetricsCollectordoes not record blocked connections
- We found no (supported?) way to add a
Describe the solution you'd like
- Track/Record blocked connections in
MetricsCollector- I've drafted a proposal and would be happy to file a PR for this to get your opinion - Optionally: Consider adding a default
BlockedListenertoAMQConnectionthat at the very least logs a warning upon blocking