[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [milo-dev] OpcUaCilentConfig
|
Setting it to be quick like that might work better to detect when the server is actually disconnected but not as well if a server is temporarily busy and not able to respond.
Also make sure that you adjust the keepAliveTimeout setting as well because you don’t the interval to be shorter than the timeout.
Or just leave all the default values in place, they seem to work reasonably well. This is a secondary mechanism for detecting the connection is lost, for when a VPN connection is cut or something like that and the sockets aren’t closed immediately.
>
> On Feb 18, 2021, at 03:10, Jakub Znamenáček <znamenacekjakub@xxxxxxxxx> wrote:
>
>
> Thanks for your reply,
>
> So if I am right when I set keepAliveInterval to 1s and keepAliveFailuresAllowed to 5 it will be similar to keepAliveInterval set to 5s but it will just check multiple times so the first approach is better. (The connection will be „marked as disconnected“ after same time)
>
> Is this correct
>
> Jakub Znamenáček
>> On 18. 2. 2021 12:03 +0100, milo developer discussions <milo-dev@xxxxxxxxxxx>, wrote:
>>
>> the client will read the server State variable periodically (at KeepAliveInterval) and if it fails consecutively a number of times that exceeds this value the client will reconnec
> _______________________________________________
> milo-dev mailing list
> milo-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/milo-dev
