Other Considerations for Using Fail-Fast Mode with Audit Logging
The audit logging database may become unavailable because there is a problem with the database itself or because there has been an interruption in connectivity to the database.
If a database problem caused the database to be unavailable, an attempt to write to the database usually fails quickly, which causes the functional alias to enter fail-fast mode quickly.
If a network problem caused the database to be unavailable, it may take several seconds to a few minutes for an attempt to write to the database to fail. The first attempt to write to the database after network connectivity is lost causes the functional alias to enter fail-fast mode. However, while the functional alias is waiting for the initial failure to return, additional client requests will wait. Each operating system has settings that control how long to wait for a response on a network connection. You may need to adjust these network settings in your operating system to avoid a long wait before the functional alias enters fail-fast mode
If the database is still available and the functional alias can establish a connection to it, but the database has become slow or unresponsive, there are two connection properties that you can set on the database URL to avoid long pauses:
LoginTimeout specifies the maximum number of seconds that Integration Server will wait for a new connection to be returned from the database.
QueryTimeout specifies the maximum number of seconds that a read or write to the database must complete in before it is rolled back.
These properties are appended to the database URL as follows:
;LoginTimeout=N;QueryTimeout=M
Where N is the number of seconds for connections to timeout and M is the number of seconds for queries or updates to timeout, respectively.
For example:
jdbc:wm:dbProvider://your-db-host:1521;ServiceName=your-db-svc;LoginTimeout=5;QueryTimeout=3
These properties are set in the Database URL field of the Settings > JDBC Pools > Connection Aliases page.
Note: Software AG recommends that you create a separate JDBC Pool Alias for use by the ISCoreAudit JDBC Functional Alias. This way, the LoginTimeout and QueryTimeout settings will affect audit logging only.