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
I am oublishing some OPC UA info on a Web Socket.
The Websocket Server stops sending message when the pipeline instantiating it is stopped and restarted even without any modification. I have to redeploy Stream pipe and reimport everything than it works again for the first run of the pipeline instantiating the Web Socket. If I stop/start it again, I have to redeploy again...
How to reproduce?
Instantiate a WS in a pipleline together with an OPC UA Data adapter and a Projection Data Processor to select what data to send to WS.
Run the pipeline
Check it is sending messages with wscat -c ws://xxx.xxx.xxx.xxx:xxx
Stop and start the pipeline and check again with wscat -c ws://xxx.xxx.xxx.xxx:xxx
Expected behavior
It seems that the pipeline is loosing the connection to the WS once stopped
Additional technical information
No response
Are you willing to submit a PR?
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Apache StreamPipes version
dev (current development state)
Affected StreamPipes components
Backend
What happened?
I am oublishing some OPC UA info on a Web Socket.
The Websocket Server stops sending message when the pipeline instantiating it is stopped and restarted even without any modification. I have to redeploy Stream pipe and reimport everything than it works again for the first run of the pipeline instantiating the Web Socket. If I stop/start it again, I have to redeploy again...
How to reproduce?
Instantiate a WS in a pipleline together with an OPC UA Data adapter and a Projection Data Processor to select what data to send to WS.
Run the pipeline
Check it is sending messages with wscat -c ws://xxx.xxx.xxx.xxx:xxx
Stop and start the pipeline and check again with wscat -c ws://xxx.xxx.xxx.xxx:xxx
Expected behavior
It seems that the pipeline is loosing the connection to the WS once stopped
Additional technical information
No response
Are you willing to submit a PR?
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: