Remote Persistence Service Timeout

[efimParticipant]

Hi,

a strange thing with Timeout for Remote Pers. Service takes place.
If no connection to service (IIS finished), the EndPointNotFound Exception comes on my system with delay appr. 23 seconds. As I understood WCF it should come immediately, and it is the case with my other services than RemotePS. I was unable also to influence it with neither OpenTimeout nor SendTiemeout anyway. I

What’s the matter?

Efim

[AdminKeymaster]

The communication over SSL is naturally failing once in a while due to key renewal. To mitigate issues with such normal and expected communication drops we retry the call 5 times before giving up.
I guess that is what you see as the longer time-out.

[efimParticipant]

Is it somehow controllable? It could be of interest for offline scenarios, e.g. polling RemotePS to get changes made by other clients

Efim

[AdminKeymaster]

Well it was not – but will be in tomorrows build:

PersistenceMapperWCFClient
///

/// How many times should we try to established connection if it failes
/// Connection will fail when SSL keys must be renewed and we want to reconnect to get new keys
///

public int FailedConnectionRetryTimes

///

/// How long should we try max in seconds before giving up
/// Connection will fail when SSL keys must be renewed and we want to reconnect to get new keys
///

public int FailedConnectionRetryMaxSeconds

[efimParticipant]

Thanks!

[efimParticipant]

Hi Hans,
what is the relation btw. these 2 settings:

1. Not concurrent: the whole delay time is product FailedConnectionRetryTimes * FailedConnectionRetryMaxSeconds
2. Concurrent: the whole delay time is minimum of Time(FailedConnectionRetryTimes) and FailedConnectionRetryMaxSeconds
3. Concurrent: the whole delay time is maximum of Time(FailedConnectionRetryTimes) and FailedConnectionRetryMaxSeconds
4. Something else?

[AdminKeymaster]

It tries set times, during maximum set time. So if the time is reached before total tries it gives up

[Author]

Posts