Session timeout error when working with large amount of data

IBM® Security Guardium® Key Lifecycle Manager operations such as, backup, restore, and export of device group, might time out when performed on large amount of data.

Long running IBM Security Guardium Key Lifecycle Manager operations might time out with an error message. For example:
[10/21/08 14:28:41:693 CDT] 00000020 TimeoutManage I   
WTRN0006W: Transaction 00000110001 has timed out after xxx seconds.
To resolve this error, configure the transaction timeout interval to a larger value by using these steps:
  • Using graphical user interface
    1. Log in to the IBM Security Guardium Key Lifecycle Manager graphical user interface.
    2. Click the Configuration tab.
    3. In the left panel, click Key Serving Ports.
    4. In the TLS timeout (in minutes) field, increase the timeout value. By default, it is set to 10 minutes and can be set to a value between 1-120 minutes.
    5. Click OK.
    6. Retry the operation that you want to perform on the large amount of data.
  • Using REST interface
    1. Open a REST client. See Using Swagger UI.
    2. Run the Update Config Property REST Service to update the TransportListener.ssl.timeout property. For example, you can send the following HTTP request:
      PUT https://localhost:port/SKLM/rest/v1/configProperties
      { "TransportListener.tcp.timeout" : "60"} 
    3. Retry the operation that you want to perform on the large amount of data.
Table 1. Topic change log
Date Change description
19 Nov 2021 Updated the steps for increasing the timeout interval. Removed the WebSphere® Integrated Solutions Console steps.
10 Sept 2021 Initial version.