Node RED OPC UA connection auto close for browse node

Industrial
1

Hi, Is there any default mechanism that Node-RED auto closes the connection opened by the browse node?

As per the source code mentioned here node-red-contrib-opcua/103-opcuabrowser.js at 1f7d4c7f22e97e5a09eaba2185720ec365375b13 · mikakaraila/node-red-contrib-opcua · GitHub
only the session is getting closed rather than the connection which is causing more open connections.

Can someone throw some light here that is there any default connection timeout settings that can be applied here? Or is it the only way to programmatically close the connection?

Thanks in advance for your help.

2

Hi. This is something you will probably need to ask in the GitHub issues pages for that node.

3

Hi @Steve-Mcl - I have mentioned the Github link just for reference. The prime ask is still the same .
" Is there any default mechanism that Node-RED auto closes the connection opened by the browse node" OR " Any specific reason why the connection opened by the browse node is not auto closed?

4

Node-red has a close event that is called when a node is re-deployed or removed but not an auto close event. Ultimately though, it would depend on the contrib nodes' author writing the appropriate code to close this connection (assuming that is the real issue).

Possibly a design decisions or an oversight by the contrib nodes' author.

In short, this is something the nodes author needs to answer. If you haven't already, then I suggest you raise this as an issue on the GitHub issues pages for that node

1 Like
5

Client will open session and it contains parameters like session timeout but also keepalive flag. Keepalive will keep session open even there is not other activity. Session that uses subscription it is needed to keep it open with keepalive as there can be longer time without any value updates.

6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.