Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heartbeat #239

Open
cziepemarex opened this issue Jul 10, 2024 · 0 comments
Open

Heartbeat #239

cziepemarex opened this issue Jul 10, 2024 · 0 comments

Comments

@cziepemarex
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant