node-red / node-red/node-red-nodes
node-red-node-mqlight - reconnect after errors or disconnections
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
We are experiencing frequent disconnections in our Bluemix Mqlight service - at least once a day. I don't know whether this is the expected behaviour or its just a temporary issue due to some maintenance work.
We are also delivering empty messages every 15 seconds to keep the connection alive, but it doesn't help.
Anyway, it would be great if node-red-node-mqlight would automatically recreate the client when an error happens (after a 1-second timeout to avoid infinite loops). Right now we are restarting the whole server when the disconnection happens.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the node-red-node-mqlight client lifecycle and its error or disconnection handling. Check how the Bluemix Mqlight client is created and what currently happens after a connection failure. Done means the client is recreated after errors or disconnections with a one-second delay, without requiring a full server restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100