.NET client: blocking in connection.dispose method about discussions

[michaelklishin]

Thank you for your time.

Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. GitHub issues are not used for questions, investigations, root cause analysis, discussions of potential issues, etc (as defined by this team).

We get at least a dozen of questions through various venues every single day, often light on details.
At that rate GitHub issues can very quickly turn into a something impossible to navigate and make sense of even for our team. Because GitHub is a tool our team uses heavily nearly every day, the signal/noise ratio of issues is something we care about a lot.

Please post this to rabbitmq-users.

Thank you.

[michaelklishin]

I'm afraid we can only speculate with this much information. IConnection#Close is the way close a connection, not IConnection#Dispose. IConnection#Abort is a more aggressive way that ignores exceptions. Both should provide an override that allows you to specify a suitable timeout. As with heartbeat timeouts, we highly recommend against timeouts that are lower than 5 seconds.

There can be a broad number of reasons for a timeout, from a genuine connection interruption to a resource alarm in effect that prevents target node from reading any data coming from clients unless the alarm clears.

[Ivony]

I found a manifestation, it's have to do with Flow Control.
when the connection state is flow, it's blocking and cannot Dispose or Abort.

Thank you very much.