9.3 Configuring WebSphere time-out settings

Creating a large number of users can be done by using a single invocation of the CreateLocalUsers API. The API is expected to persist all the new users or roll back all changes in the event of a failure. Therefore, the API is required to operate in a single transaction to support rollback. Because a transaction’s lifetime is limited by the application server settings (usually 30 seconds), the number of inserts that can be performed in the given time frame is limited. As a result, bulk insert APIs such as CreateLocalUser fail when the number of users exceeds a certain limit. This limit is decided again by the transaction’s lifetime.

You must modify the following time-out settings:

  • Transaction time-out value

  • CORBA time-out value

  • SOAP request time-out value

Configure transaction time-out

  1. In the WebSphere Administrative Console navigation tree, do the following for your application server:

    Click Servers > Server Types > WebSphere application servers

  2. Click the server name in the right pane.

  3. Under Container Settings, click Container Services > Transaction Service.

  4. Under General Properties, in the Total transaction lifetime timeout box, type 300 (or higher).

  5. Ensure that the value in the Maximum transaction timeout box is greater than or equal to the Total transaction lifetime timeout.

  6. Click OK or Apply and the n click Save directly to master configuration.

Increase the CORBA time-out value

  1. In the WebSphere Administrative Console navigation tree, do the following for your application server:

    Click Servers > Server Types > WebSphere application servers

  2. Click the server name in the right pane.

  3. Under Container Settings, click Container Services > ORB Service.

  4. Under General Properties, in the Request timeout box, type 360 and, in the Locate Request Timeout box, type 300.

  5. Click OK or Apply and then click Save directly to master configuration.

increase the SOAP request time-out value

  1. Navigate to your [appserver root] directory and search for all files named soap.client.props. Multiple files may have this name. For example, the following files may require modifications. Modification of the template profile definitions is required only if profiles will be created using these templates:

    • [appserver root]/profileTemplates/default/documents/properties/soap.client.props

    • [appserver root]/profileTemplates/cell/default/documents/properties/soap.client.props

    • [appserver root]/cip/profileTemplates/minimal/documents/properties/soap.client.props

    • [appserver root]/profiles/AppSrv01/properties/soap.client.props

  2. Open the file in a text editor, find the com.ibm.SOAP.requestTimeout property, change the value from 180 to 1800, and then save the file(s).

    Note: Repeat this step for each file.

  3. In the WebSphere Administrative Console navigation tree, do the following for your application server:

    (WebSphere 6.1) Click Servers > Application servers.

    (WebSphere 7.0) Click Servers > Server Types > WebSphere application servers.

  4. Click the server name in the right pane.

  5. Under Server Infrastructure, click Administration > Administration Services.

  6. Under Additional Properties, click JMX connectors and, in the right pane, click SOAPConnector in the list.

  7. On the next screen, click Custom Properties, and then click requestTimeout in the list.

  8. Under General Properties, in the Value box, change 600 to 1800.

  9. Click OK or Apply and then click Save directly to master configuration.

Note: Increase the SOAP request time-out value beyond 1800 if EAR deployment fails with The system failed to make the SOAP RPC call: invoke error.

    // Ethnio survey code removed