Manage connection properties

The ability to manage connection properties enables you to prevent clients from locking up the server. It also ensures that the administrator always has access to the server in the cases that the backend is kept busy with long-running tasks. Management of the connection properties is done through the Web administration tool.

To set connection properties, perform the following steps:

1. Expand the Server administration category in the navigation area and click Manage connection properties.
   Note:
   To change server configuration settings using the tasks in the Server administration category of the Web Administration tool, you must authenticate to the server as an i5/OS user profile that has *ALLOBJ and IOSYSCFG special authorities. This can be done by authenticating as a projected user with the password for that profile. To bind as a projected user from the Web administration tool, enter a username of the form os400-profile=MYUSERNAME,cn=accounts,os400-sys=MYSYSTEM.COM, where MYUSERNAME and the MYSYSTEM.COM strings are replaced with your user profile name and the configured system projection suffix, respectively.
2. Select the General tab.
3. Set the anonymous connection setting. The Allow anonymous connections check box is already selected for you so that anonymous binds are allowed. This is the default setting. You can click the check box to deselect the Allow anonymous connections function. This action causes the server to unbind all anonymous connections.
   Note:
   Some applications might fail if you disallow anonymous binds.
4. In the Cleanup threshold for anonymous connections field, set the threshold number to initiate the unbinding of anonymous connections. You can specify a number between 0 and 65535 .
   Note:
   The actual maximum number is limited by the number of files permitted per process. On UNIX systems you can use the ulimit -a command to determine the limits. On Windows systems this is a fixed number.
   The default setting is 0. When this number of anonymous connections is exceeded, connections are cleaned up based on the idle timeout limit that you set in the Idle time out field.
5. In the Cleanup threshold for authenticated connections field, set the threshold number to initiate the unbinding of authenticated connections. You can specify a number between 0 and 65535 .
   Note:
   The actual maximum number is limited by the number of files permitted per process. On UNIX systems you can use the ulimit -a command to determine the limits. On Windows systems this is a fixed number.
   The default setting is 1100. When this number of authenticated connections is exceeded, connections are cleaned up based on the idle timeout limit that you set in the Idle time out field.
6. In the Cleanup threshold for all connections field, set the threshold number to initiate the unbinding of all connections. You can specify a number between 0 and 65535 .
   Note:
   The actual maximum number is limited by the number of files permitted per process. On UNIX systems you can use the ulimit -a command to determine the limits. On Windows systems this is a fixed number.
   The default setting is 1200. When this total number of connections is exceeded, connections are cleaned up based on the idle timeout limit that you set in the Idle time out field.
7. In the Idle timeout limit field, set the number of seconds that a connection can be idle before it is closed by a cleanup process. You can specify a number between 0 and 65535 .
   Note:
   The actual maximum number is limited by the number of files permitted per process. On UNIX systems you can use the ulimit -a command to determine the limits. On Windows systems this is a fixed number.
   The default setting is 300. When a cleanup process is initiated, any connections, subject to the process, that exceed the limit are closed.
8. In the Result timeout limit field, set the number of seconds that are allowed between write attempts. You can specify a number between 0 and 65535 . The default setting is 120. Any connections that exceed this limit are ended.
   Note:
   This applies to Windows systems only. A connection that exceeds 30 seconds is automatically dropped by the operating system. Therefore, this Result timeout limit setting is overridden by the operating system after 30 seconds.
9. Click the Emergency thread tab.
10. Set the emergency thread setting. The Enable emergency thread check box is already selected for you so that the emergency thread can be activated. This is the default setting. You can click the check box to deselect the Enable emergency thread function. This action prevents the emergency thread from being activated.
11. In the Pending request threshold field, set the number limit for work requests that activate the emergency thread. Specify a number between 0 and 65535 to set the limit of work requests that can be in the queue before activating the emergency thread. The default is 50. When the specified limit is exceeded, the emergency thread is activated.
12. In the Time threshold field, set the number of minutes that can elapse since the last work item was removed from the queue. If there are work items in the queue and this time limit is exceeded, the emergency thread is activated. You can specify a number between 0 and 240 . The default setting is 5.
13. Select from the drop-down menu, the criteria to be used to activate the emergency thread. You can select:
    • Size only: The emergency thread is activated only when the queue exceeds the specified amount of pending work items.
    • Time only: The emergency thread is activated only when the time limit between removed work items exceeds the specified amount.
    • Size or time: The emergency thread is activated when either the queue size or time threshold exceeds the specified amounts.
    • Size and time: The emergency thread is activated when both the queue size and the time threshold exceed the specified amounts.
    Size and time is the default setting.
14. Click OK

For more information, see Manage server connections.