Timeout Options for ICM
The ICM have different timeouts, which are controlled by profile parameters
- Timeout for opening connection: icm/conn_timeout
- Keepalive timeout for the network connection: icm/server_port_<xx> – option TIMEOUT and icm/keep_alive_timeout
- Processing timeout in the back end: icm/server_port_<xx> – option PROCTIMEOUT
The timeouts described here are valid only for HTTP(S), not for other protocols.
Timeout for opening connection: Parameter icm/conn_timeout
This parameter is used to set the timeout when the connection is opened. By default, if the timeout is exceeded, an error page with the message “404 Resource not found: Partner not reached” is displayed.
Exceeding this timeout does not therefore result in the error message “500 Connection timed out”.
NOTE: Because of this I didn’t made any change in this parameter.
Keep-alive timeout Option TIMEOUT or profile parameter icm/keepalive_timeout
The keep-alive timeout specifies how long the network connection remains open once the request has been successfully processed.
The keepalive timeout can be defined globally for all ICM services by parameter icm/keep_alive_timeout. It can also be defined for individual services by parameter icm/server_port_< xx > = ...,TIMEOUT=< s >. This overrides parameter icm/keep_alive_timeout for the individual service.
End of the recommendation.
The time period is set in parameter icm/server_port_< xx > with option TIMEOUT (in seconds)
Value -1 deactivates the timeout.
Depending on the type of network connection (internal, LAN, WAN, it may be best to increase the parameter value. The value should not be less than 10 seconds. If, on the other hand, a value is too high, the network connections will be very slow and the performance of the server will suffer.
Processing timeout Option - PROCTIMEOUT
The processing timeout specifies the timeout between sending an HTTP request and receiving an HTTP response.
- ICM as HTTP Server: If the ICM receives a request and has forwarded it for processing (to AS ABAP or AS Java), the ICM waits for the server response until the timeout has expired. The work process context is then closed, the client is notified with a Connection Timeout message
- ICM as HTTP Client: If the ICM for the HTTP request concerned is used as a client, and forwards an outbound request from the SAP NetWeaver AS, the processing timeout specifies the time the ICM waits for until there is a response from the network. This can also be exceeded if there are long-running applications in the network.
The value is specified with the parameter <proctimeout> in seconds. Value -1 deactivates the timeout.
If the PROCTIMEOUT parameter is not specified, TIMEOUT (or icm/keepalive_timeout) defines the keep-alive timeout as well as the processing timeout. Moreover, the keep-alive timeout is restricted to a maximum of 60 seconds.
The recommend value to that parameter as follows:
icm/server_port_0 = PROT=HTTP, PORT=80$$, TIMEOUT=60, PROCTIMEOUT=600
We can allow a maximum processing time of 10 minutes.
Security session timeout
The parameter http/security_session_timeout defines the maximum time period between the receipt of two HTTP requests (with valid security session ID). After this period has expired, all application contexts that are connected with a security session on this application server (if you are using stateful Web applications) are closed (and resources that are connected with these sessions are released.
Please check this KBA if you experience timeout:
1948291 - User session (HTTP/SMTP/..) closed after timeout