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

when to call quit() #142

Open
createthis opened this issue Feb 16, 2022 · 0 comments
Open

when to call quit() #142

createthis opened this issue Feb 16, 2022 · 0 comments

Comments

@createthis
Copy link

From the documentation: https://github.com/smrchy/rsmq#quitcallback

Disconnect the redis client. This is only useful if you are using rsmq within a script and want node to be able to exit.

Our environment is exhibiting redis connection leaks. We currently encapsulate RSMQ in a class. We instantiate that class using new in a local scope and perform some RSMQ interactions. The instantiated object passes out of scope and I assume is garbage collected, however the redis connection for RSMQ seems to hang around.

The documentation seems to imply that quit() should never have to be used and garbage collection of the connection will happen automagically, but that isn't what we're seeing. Is the documentation wrong?

Thoughts?

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