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
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?
The text was updated successfully, but these errors were encountered:
From the documentation: https://github.com/smrchy/rsmq#quitcallback
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?
The text was updated successfully, but these errors were encountered: