database-request-timeout
Section: settings
Default Value: 0
Valid Values: Any integer from 0 to 1,800
Changes Take Effect: Immediately
Specifies, in seconds, the maximum allowable delay after which certain
database requests are cancelled, and an error is returned to the client. With the
default value of 0, there is no timeout.
In particular: when the value is greater than zero, Interaction Server cancels
any database request that is blocking a reply to an Interaction Server client and
is taking longer to execute than the specified timeout. Interaction Server also
sends a Database request timed out error to the client in question and prints the
standard "alarmable" message (log message ID 25037) in its logs.
8.5.104.05
Interaction Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 08/04/15 | General | X | X | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- This version supports dates up to the year 2999 on Windows platforms or up to the year 9999 on other platforms. Previously the dates were limited to year 2037. Among the drawbacks of that limit was that it prevented scheduling interaction processing far into the future.
Resolved Issues
This release contains the following resolved issues:
This release improves the handling of reconnection events on secure channels. Previously, in the rare circumstance of a relayed reconnection, Interaction Server exited unexpectedly. (ESR-10358)
This release improves the handling of delayed responses from the database when the database-request-timeout option is set to a non-zero value. Interaction Server now:
- Properly initiates the SQL query for a segmentation request when it is switched to primary mode in an HA environment. (ESR-10159)
- Disconnects all reporting clients when it is switched to backup mode in an HA environment. (ESR-9902)
- Properly exits upon receiving a termination command even if it never received a response for some tasks for the database. (ESR-10134)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.104.05.