Node red - opc ua : BadTooManySessions
Hello,
When i try to connect to the opc ua server on the plc next via uaexpert i get 'BadTooManySessions'.
When restarting node red i first get 'BadTooManySessions' in the debugwindow but when i get my first value it is printed propperly.
i dont know how this is possible.
where can i see how many sessions are running and how do i close these sessions if this is possible.
Thank you in advance
When i try to connect to the opc ua server on the plc next via uaexpert i get 'BadTooManySessions'.
When restarting node red i first get 'BadTooManySessions' in the debugwindow but when i get my first value it is printed propperly.
i dont know how this is possible.
where can i see how many sessions are running and how do i close these sessions if this is possible.
Thank you in advance
Comments
Details can be found in the following How To (you'll need to copy and paste this link, sorry):
You cannot reset individual sessions, but the session timeout is set to 20 minutes by default.
This means that even if a client does not close the session properly, the session is automatically terminated after this time and the server can then be reached again.
The maximum number of sessions for each PLC type is listed in the PLCnext Info Center:
https://www.plcnext.help/te/Service_Components/OPC_UA_Server/PLCnext_Control_OPC_UA.htm
Hi,
is there a possibility of shortening the timeout? Unfortunately, when are we developing in python the VS Code does not gracefully cut the connection every time the debug mod is reset.
Thank you.
I'm not sure if the behaviour of the server has changed since that earlier answer, but the latest information, here ...
... means that it's possible for the Client to request the session timeout. If the server doesn't accept your client's requested timeout value, please let us know.
(and sorry for the weird formatting on this page ...)
We were successful in establishing a connection with 10s TTL.
Thank you for the hint.