You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using this extension in Azure on a function app with a RabbitMq that resides on an AWS server. Every so often we get problems with the functions not triggering when a new item enters a queue.
Doing some reading on this it appears that AWS will close TCP connections that has inactivity for a while. One way to stop it from doing this is to introduce a heartbeat check every so often so it keeps the connection alive.
Looking at the code, when the connectionfactory is created there's no requested heartbeat value set. Is there a reason for this?
I'd love to be able to set this as the functions are quietly dropping connections without any warnings.
The text was updated successfully, but these errors were encountered:
I'm using this extension in Azure on a function app with a RabbitMq that resides on an AWS server. Every so often we get problems with the functions not triggering when a new item enters a queue.
Doing some reading on this it appears that AWS will close TCP connections that has inactivity for a while. One way to stop it from doing this is to introduce a heartbeat check every so often so it keeps the connection alive.
Looking at the code, when the connectionfactory is created there's no requested heartbeat value set. Is there a reason for this?
I'd love to be able to set this as the functions are quietly dropping connections without any warnings.
The text was updated successfully, but these errors were encountered: