Technical instruction - Timeout used in Signifikant

Overview

Some operations are limited in time by defining a timeout. Without it, a user may have to wait a long time for a failing operation where an response is missing. A short timeout may break an operation where the processing takes a long time, but no error occurs. Depending on database size, configuration can be changed to allow a longer waiting time.

Server.config

Other configuration for the application is found in a different configuration file, normally here. It defines timeout values for publication and validation, for database transactions.

SOAP interface defined in Start.exe.config

Manager client program timeout is defined in its configuration file. SOAP operation timeout is defined in binding elements, name = AssertSoapServiceBinding or AssertSoapServiceBindingSSL depending on the schema used for client/server communication. I.e. HTTP or HTTPS address to the server.

Validation is a synchronous operation that may need a long timeout. Publication is also a long running operation, but it is run as an asynchronous operation, so a SOAP timeout is not an issue.

Publisher

Set PublisherCommandTimeout in server.config to setup a timeout for all database queries during the publication process. The element holds a timeout value as a number of seconds.

Validation

Validate operation, i.e. when issue a Validate on the whole database, uses the PublisherCommandTimeout setting for SOAP send/receive timeout. It will override the binding defined in the clients configuration file.

Validators database queries uses same parameter, PublisherCommandTimeout, for database accesses.

Also check the log file for duration figures, to get an estimate on what a sufficient timeout may be.

Database queries

The Manager program requests data to repositories, from the server. The server uses the CommandTimeout value from server.config for database queries. The element holds a timeout value as a number of seconds.