Log In
Register
Forum
Topic RSS
15:18, EEST
February 21, 2014
Offline
Hi,
the following may be a trivial question and I may possibly have overlooked the obvious solution…
I would like to reliably monitor the connection status of an SDK based OPC UA client to a server.
– the isConnected() can be used to check the connection status from time to time
– the ServerStatus (via ServerStatusListener)
– the ServerState (via ServerStatusListener)
The main use case it the detection of network related communication problems and a low latency information of the user, without waiting for network timeouts or SDK session reconnects.
Thanks for your support
16:38, EEST
April 3, 2012
Offline
Hi,
Good Question.
Basically those 3 are the intended ways, but basically they will only fail once the ServerStatus read fails (if nothing else). Due to some historical stuff e.g. separate stacksdk layers and the need to support multiple connection protocols (even though in my personal opinion opc.https basically should never be used) that is the only reliable way. We are aware that this could use some improvements.
15:54, EEST
December 21, 2011
Offline
Yes, the ServerStatusListener is the best way to get informed of connection breaks. The client sends a read request to ServerStatus every StatusCheckInterval and that times out after StatusCheckTimeout. If you need faster reaction, you can reduce that timeout from the default 10 seconds, but that may create more false alerts. And the client will also start an automatic reconnection whenever the status read fails (or times out).
onServerState is called only when the state changes (from Running to CommunicationFault, for example).
onServerStatus is called after every read, since it contains CurrentTime which should be constantly changing in the server.
1 Guest(s)
