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.
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.