Using Guaranteed Delivery with a Stateful or Stateless Cluster
When you use clustering, guaranteed delivery stores information about requests for all clustered servers in a shared, centrally located database. Because the information is stored centrally, guaranteed delivery uses a locking mechanism to synchronize updates to the database.
Attempts to update the database might time out. As a result, the server may require several attempts to complete a request. You can limit how long a cluster server sleeps between attempts to place an update lock on the database. In addition, you can set a maximum time limit after which the server overrides a lock on the database held by a non-responsive server in order to complete the update.
To configure cluster database locking
1. In Integration Server Administrator, go to Settings > Extended and locate the watt.server.tx.cluster.lockTimeoutMillis parameter. If this parameter does not exist, add it. Set it as follows:
Set this parameter: | To specify |
watt.server.tx.cluster. lockTimeoutMillis
| The number of milliseconds a cluster server waits between requests to place an update lock. |
2. To set how long a cluster server will wait before overriding a lock, locate the watt.server.tx.cluster.lockBreakSecs parameter. If this parameter does not exist, add it. Set it as follows:
Set this parameter: | To specify |
watt.server.tx.cluster. lockBreakSecs
| The number of seconds a cluster server waits before overriding a lock. |
For more information about using the Extended settings page to configure the Integration Server, see
3. Click Save Changes and restart the Integration Server.