Enabling dynamic configuration of WebSphere eXtreme Scale Client for .NET

You can configure WebSphere® eXtreme Scale Client for .NET to dynamically detect modifications that are made to the property values in the client properties file. You do not need to restart the existing connection to the data grid for the changes to take effect.

1. Set the value of the enableDynamicConfiguration property in your client properties file for WebSphere eXtreme Scale Client for .NET to true.

   enableDynamicConfiguration

   When set to true, any changes that are made to the requestRetryTimeout property in the client properties file are detected dynamically. The new property value is used immediately to calculate the new request retry timeout value.

   Default: false

   Valid values: true, false

2. Update the value of the requestRetryTimeout property in your client properties file.

   requestRetryTimeout

   Specifies how long to continue processing a request (in milliseconds) after an exception occurs.

   Default: -1

   Valid values:

   • A value of 0 indicates that the request should fail fast and skip over the internal retry logic.
   • A value of -1 indicates that the request retry timeout is not set, meaning that the request duration is governed by the transaction timeout. (Default). The following levels of checking the request retry timeout are used to determine the default behavior:
     • Session instance requestRetryTimeout value
     • Client properties file requestRetryTimeout value
     • If neither of the previous values are set, then the lowest value between the transaction timeout value and 30 seconds is selected. For example, if the transaction timeout value has the default value of 10 minutes, then the request times out at 30 seconds. Alternatively, if you set the transaction timeout value to 20 seconds, then the request times out after 20 seconds.
   • A value over 0 indicates the request entry timeout value in milliseconds. Exceptions that are not successfully created are returned. Even when exceptions, such as DuplicateException, are tried again, they are also returned when they do not succeed. The transaction timeout is still used as the maximum time to wait.