Timeouts - ICM & HTTP

[Former Member]

Hi,

The ICM_HTTP_TIMEOUT in the note 824544 and the HTTP_TIMEOUT to be configured via SXMB_ADM seems to be different. First one is for synchronous calls via ICM and the other for time between two data packages.

Also the ICM synchronous timeouts (keep_alive & processing timeout) can be changed via RZ10 (profile parameter).

I am getting a timeout in ICM. Hence, going to SMICM->GOTO->Services->HTTP->Change seems to be the appropriate option.

Please confirm.

Also confirm whether my understanding above is correct in all aspects.

Thanks,

John

[michael_mulvey]

Hi,

The ICM considers two basic timeout parameters:-

(1) Processing timeout:-

The processing timeout is the timeout between the HTTP request

being issued and the HTTP response being received.

- If the ICM acts as a server for the relevant HTTP request

(that is, if it forwards an incoming request to SAP NetWeaver

AS), the processing timeout specifies the time that the ICM

will wait until a response is received from the SAP Web

Application Server (AS ABAP or AS Java). This time my be

exceeded in the case of long-running applications in AS ABAP

or in AS Java (up to 6.40 "J2EE Engine"). If the processing

timeout is exceeded, the ICM sends the client an HTTP response

with the error code "500 Connection timed out".

- If the ICM serves as a client for the relevant HTTP request

(that is, when it forwards outgoing requests from the SAP

NetWeaver Application Server), the processing timeout states

the amount time that the ICM waits until a response is

received from the network. This interval may also be exceeded

in the case of long-running applications in the network.

(2) Keepalive timeout

The keepalive timeout specifies how long the network should

remain open after a request has been processed successfully so

that the TCP/IP connection does not have to be reestablished if

additional requests are received.

When you set the keepalive timeout, this does not normally lead

to timeout errors. You should set the keepalive timeout high

enough that the connection does not have to be reestablished for

requests that are sent within a short time of each other, but low

enough that the number of unused open TCP/IP connections is not

unnecessarily high. Exceeding the Keepalive timeout should never

cause an error.

SAP Note [824554|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_cst/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383234353534%7d] - "ICM and SAP Web Dispatcher Timeout Parameter" gives a VERY good overview of the parameters and how to use them.

Michael