Show TOC

Background documentationrdisp/http_min_wait_dia_wp Locate this document in the navigation structure


If an HTTP(S) or SMTP request is to be processed by a dialog work process, the Dispatcher checks how many dialogs are free. This parameter controls how many dialog work processes are to be kept free for other users. If there are no more free dialog work processes for HTTP(S)/SMTP, the Dispatcher sends no more resources to the caller.

This protects the server from being overloaded with HTTP(S)/SMTP requests.


The parameter is only evaluated, if the check is activated by rdisp/http_check.

The absolute number of dialog work processes is determined by the parameter rdisp/wp_no_dia.


Work area



Integer value

Standard value


Dynamically changeable


Value Range and Syntax

You can specify a number between 0 (default) and rdisp/wp_no_dia -1 (the number of configured dialog work processes).

You can set the parameter dynamically in productive operation (transaction RZ11). Though these settings will be lost when the instance is started up the next time.

The parameter rdisp/rfc_min_wait_dia_wp makes the same checks but for RFC requests.


There are 10 dialog WPs, and rdisp/http_min_wait_dia_wp = 4.

If the Dispatcher receives an HTTP request for processing from the ICM and there are currently four dialog work processes free, the request is put in the queue and not processed until there are at least 5 dialog WPs free.

More Information

Note the following documentation associated with this parameter: