Understanding Database Timeouts

We monitor database accesses in terms of time. To do this, the timeouts systemDBRequestWarnTimeout and systemDBRequestTimeout must be configured in the Designer Instance Configuration. If the user starts a database request, and systemDBRequestWarnTimeout expires, a dialogue box with a warning message appears. In this dialogue box, you can decide whether to continue with the request or cancel it. If a database query is started automatically, as a manager process for example, the warning appears as a log entry and the request either ends before systemDBRequestTimeout or is canceled. For this reason, systemDBRequestWarnTimeout must always be set lower than systemDBRequestTimeout. Timeouts defined in JDito Processes refer to systemDBRequestTimeout. Here it is also important to ensure that systemDBRequestTimeout is always set higher than systemDBRequestWarnTimeout.

If the timeouts do not occur in a valid sequence, warnings are written to the log and an attempt from the system is made to start the database query with default timeouts.

Screenshot:

Schematic representation:

    |-----------------------------> Timeline
sec:0........10..................30  
    |         |                   |
    |         |                   |
    |         |                   systemDBRequestTimeout 
    |         |                   The database access is 
    |         |                   definitely cancelled.
    |         |
    |         systemDBRequestWarnTimeout
    |         Dialog pops up
    |         and Log Message 
    |          
    The database access 
    starts running        

The following timeouts all refer to systemDBRequestTimeout:

calendarTimeout mailGlobalTimeout (expert parameter)
serverFarmTimeout (expert parameter)
databaseAuditDBTimeout (expert parameter)
databaseDBSyncDBRequestTimeout (expert parameter)
timeout (expert parameter in _____PREFERENCES_PROJECT)
linkerTimeout (parameter in AliasConfiguration)