Log In
Register
Forum
Topic RSS
12:22, EEST
February 21, 2014
Offline
Good morning,
I have multiple OPC UA clients trying to connect to various OPC UA services (aka servers). In case any of the OPC UA servers does not respond, the corresponding UaClient.connect() calls *eventually* timeout (after the configured period).
Is there a way to prematurely graciously abort the client.connect() attempt? Are there any differences between the SDK versions 3.1.6 and 4.x?
Thanks,
Hans-Uwe
11:24, EEST
April 3, 2012
Offline
Hi,
Not exactly at the moment. 4.0.0 added UaClient.setConnectTimeout(…), which makes easier to set the initial connection (i.e. Socket gets initial connection) timeout. Maybe you could start with quite optimistic timeout first and then increase it if a connect fails due to that?
13:26, EEST
December 21, 2011
Offline
You can also consider running the connect method in a worker thread so that your application doesn’t need to block and wait for the call to timeout if it takes too long.
At some point we considered adding a separate connectAsync method for that, but it turned out to be very complex – especially in comparison to how simple it is to do it yourself in a worker three suitable to your application.
13:49, EEST
February 21, 2014
Offline
We have remote servers over a high latency connection – so the timeout length is indeed needed. Sometimes though, the address of the server has been incorrectly configured and the new configuration shall be picked up as quickly as possible.
The connect() attempt is already running in a worker thread. While terminating the worker thread is possible, this would be “brute force” and eventually leave some resources in an undefined state – which I’d prefer to avoid.
1 Guest(s)
