[Event Hubs] investigate connection disconnect behavior in linux

[chradek]

Some other language SDKs could keep a connection open despite a socket no longer receiving traffic in linux. A fix in those SDKs was to add an idle timeout. A quick search suggests the JS SDK already has an idle timeout of 60 seconds, but this issue is to track confirming that it is working correctly.

[chradek]

Confirmed that this is an issue in our amqp-based sdks.

We can make use of the idle_time_out parameter (supports minimum of 10 seconds) in rhea.

So far I've encountered 2 issues when trying to use idle_time_out.

amqp/rhea#264 (resolved)
Rhea now notifies when the idle_time_out has been met by dispatching a disconnected event on a connection. Previously there was no way to be notified when the idle_time_out was met.

amqp/rhea#266
There is an issue preventing us from being able to re-use a connection after the idle_time_out has been met. Since we can't use rhea's built-in reconnect and don't want to create an entirely new thea Connection object (this would be a large refactor), ideally the above issue would be addressed to unblock us. I tested the change suggested in the issue with Event Hubs and it worked well. I believe this should be our last blocker.

[chradek]

amqp/rhea#267 has been merged which fixes amqp/rhea#266, so there shouldn't be any blockers left.
Changes are in version 1.0.15 of rhea.

Next steps are:

• determine best place to expose idleTimeOut (client libraries or amqp libraries?)
• update amqp-common to pass idle_time_out as a rhea connection option.
• update core-amqp to pass idle_time_out as a rhea connection option.
• determine whether to pin rhea version in amqp libraries or ask users to reinstall node modules.

[ramya-rao-a]

Should we release an update for Service Bus with this fix?

[chradek]

#6507 updates service bus and event hubs to take in these changes.

[chradek]

This fix is present in:

• @azure/event-hubs version 2.1.4
• @azure/event-processor-host version 2.1.1
• @azure/service-bus version 1.1.2

It will also go out in the next version of @azure/event-hubs 5.x.