Closed ganesh1306 closed 4 years ago
i know these quotes from the opcua reference... they always discribe a unicorn one the one hand they say pub/sub is like fire and forget and on the other hand there should be no dataloss... if you subscribe to server state you only get notified if the server gracefully shutdown
in my opinion the easiest way is in the asyncua_client.py just read the service value cyclic and reconnect and resubscribe this catches all kinds of connection problems!
if you still want to use it like in the spec writen you need to use the low-level-api not the high-level-api which is made cover most importent features in easy to use fashion!
i agree with you using a asyncua_client.py but the sessions on the server side will increase still every time by using https://reference.opcfoundation.org/v104/Core/docs/Part4/6.7/ according to Figure 36 in the link, the session count will increase only when the connection loss happens according to me if am wrong correct me
dont understand your question!
do you mean that:
SessionTimeout
Sessions should not timeout very easily, so a timeout value of one hour is a good default value (the default also in UaClient). It is there just that the server can close sessions that have not been active (no message of any type from the client received for a longer period than SessionTimeout), because the client has died or is no longer connected to the server .
I am using prosys in that when I implemented the reconnection logic of client ,in prosys server under session section the value of session is limited to 50,
While do this implementation the session on the server side is increments in prosys.
i already anwered this question in another issue (python-opcua) or here !!! you should look in python-opcua issues your not the first one...
i need only when the server disconnects it has to connect and continue other works and create a session in the client if serves is restart
with this statement
Reconnection
i tired with this i am able to get