STOMP: "Can't subscribe, not connected" when multiple stomp in nodes are used with different topics
OlivierVerhaegen opened this issue · 0 comments
OlivierVerhaegen commented
Which node are you reporting an issue on?
stomp in
What are the steps to reproduce?
- Create a new flow
- Add 2 stomp in nodes
- Create a stomp server
- Configure the same stomp server for the 2 stomp in nodes
- Deploy
What happens?
Race conditions cause the second (or third, ...) stomp in node to try and subscribe before the connection was made to the STOMP server.
What do you expect to happen?
The subscription should only be made after successfully connection to the STOMP server.
Please tell us about your environment:
- Node-RED version: v3.0.2 & v2.2.3
- node.js version: v16.16.0
- npm version: v8.11.0
- Platform/OS: Node red docker image
- Browser: Chrome