SAP Note 824554 - ICM and SAP Web Dispatcher Timeout Parameter Version 22 Validity: 16.08.2012 - active Language English Header Data Released On Release Status Component 28.08.2012 16:38:24 Released for Customer BC-CST-IC Internet Communication Manager Other Components BC-CST-WDP Web Dispatcher Priority Category Recommendations / Additional Info Help for error analysis Symptom You want to configure the timeout settings of the Internet Communication Manager (ICM) or the SAP Web Dispatcher. The SAP Web Application Server may issue HTTP timeout error messages. The error message displayed is "500 Connection timed out" if you have not defined your own dynamic ICM error pages. If the error occurs, you can use the note to help you with troubleshooting. Other Terms keepalive, 402, 500, ICM_HTTP_TIMEOUT, ICM_HTTP_CONNECTION_FAILED Reason and Prerequisites You are using ICM Release 6.40 or higher for HTTP connections of the SAP NetWeaver Application Server. In other words, your kernel release is 6.40 or higher. Up to and including Release 7.00, ICM is only used in systems that also have an Application Server ABAP (AS ABAP), and not in systems that only have AS Java. You may also be using the SAP Web Dispatcher. Solution The note describes the following: l Client and server roles of the ICM l List of the various ICM timeout parameters l Short description of the icm/conn_timeout parameter l Explanation of "Processing timeout" and "Keepalive timeout" l Configuration of the ICM parameters for the processing timeout and the keepalive timeout l Timeout parameters in the SAP Web Dispatcher l ICM kernel patches that affect timeouts You can find detailed ICM documentation on the SAP Help Portal (help.sap.com). Client and server roles of the ICM The ICM can forward incoming HTTP connections to the SAP Web Application Server for processing. The ICM then serves as the HTTP server. The ICM can also forward outgoing HTTP connections from the SAP Web Application Server to other HTTP servers. The ICM then serves as the HTTP client. Available parameters that control ICM timeouts l icm/conn_timeout l icm/keep_alive_timeout l icm/server_port_< n > Parameter icm/conn_timeout icm/conn_timeout is used to set the timeout when setting up the connection. If the timeout is exceeded, an error page is generally displayed with the information "404 Resource not found" "Partner not reached". for example.pfl). if it forwards an incoming request to SAP NetWeaver AS). If you have not set the PROCTIMEOUT parameter. l l The processing timeout is set for individual services using the following parameter: icm/server_port_ < n > = . This interval may also be exceeded in the case of long-running applications in the network.TIMEOUT=< s >. it is possible for a client to explicitly set the timeout in IF_HTTP_CLIENT. We recommend that you set the same parameters in the SAP Web Dispatcher and ICM. when it forwards outgoing requests from the SAP NetWeaver Application Server). If the ICM serves as a client for the relevant HTTP request (that is. Timeout parameter in the SAP Web Dispatcher The same timeout parameters are available for the SAP Web Dispatcher as for the ICM. If you set this parameter.. Configuration of the ICM parameters for the processing timeout and the keepalive timeout For the ICM. the processing timeout states the amount time that the ICM waits until a response is received from the network. This time my be exceeded in the case of long-running applications in AS ABAP or in AS Java (up to 6. the TIMEOUT and PROCTIMEOUT parameters of icm/server_port_ < n > control the timeouts for the relevant protocol. When you set the keepalive timeout. In addition. there have not been any known errors in ICM and Web Dispatcher timeout handling.00 and later releases. we recommend that you set the TIMEOUT and PROCTIMEOUT parameters for the relevant services so that you can configure them independent of each other.40. this does not normally lead to timeout errors.. as of release 6.. the keepalive timeout is limited to a maximum of 60 seconds.PORT=1080. the ICM sends the client an HTTP response with the error code "500 Connection timed out". You can change them in the profile file of the SAP Web Dispatcher (for example.40 "J2EE Engine").Therefore. Validity . In a system where the default timeout settings of 60 seconds for the keepalive timeout and the processing timeout are insufficient because of long-running applications.. for example. the parameters mentioned here are in the instance profile. If the processing timeout is exceeded. there are no known errors in ICM and Web Dispatcher Timeout Handling. In Release 7. You can also set it for individual services by using the following parameter: icm/server_port_ < n > = . Processing timeout and keepalive timeout The parameters icm/keep_alive_timeout and icm/server_port_< n > define the keepalive timeout and the processing timeout. the following settings: icm/server_port_0 = PROT=HTTP. provided that you have set TIMEOUT or PROCTIMEOUT. method SEND. Known Internet Explorer errors in the keepalive timeout handling Known errors in the keepalive handling from Internet Explorer are described in Note 900804. ¡ ¡ l If the ICM acts as a server for the relevant HTTP request (that is. We recommend. In addition. Known errors in ICM and Web Dispatcher timeout handling l l Since 6. However. sapwebdisp. these errors are not usually displayed as timeout errors. TIMEOUT (or icm/keepalive_timeout) defines both the processing timeout and the keepalive timeout.. but low enough that the number of unused open TCP/IP connections is not unnecessarily high. 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. The keepalive timeout can be set globally for all services of the ICM using the parameter icm/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. However. l The processing timeout is the timeout between the HTTP request being issued and the HTTP response being received.40 patch level 64. we recommend that you do not set the TIMEOUT value higher than necessary. Even if the ICM serves as client for a request.PROCTIMEOUT=600 to allow a maximum processing time of 10 minutes. it overwrites parameter icm/keepalive_timeout for the specified service. Exceeding the Keepalive timeout should never cause an error.TIMEOUT=60.. 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).PROCTIMEOUT=< s >. to the usual default value of 60 seconds. ICM distinguishes between these two types of timeout. exceeding the icm/conn_timeout does not lead to a "500 Connection timed out" error message. This document is not restricted to a software component or software component version References This document refers to: SAP Notes 1488594 PI CTC: Connection to system Integration Builder lost 1432150 XI runtime: HTTP return code 110 1352731 MOpz: Download or deployment hangs when using SLM 1347276 IC_AGENT Business Role:Pre-mature closure of IE 1162605 Network performance for CRM (IC) Webclient 1139406 CTS+: cx_ai_system_fault during import of orders 1004684 Abort of large content import and transport 981211 HTTP debugging with the new debugger is terminated 921061 How to set Timeouts in Mobile Infrastructure 906435 XI Internal HTTP Error during CALL_ADAPTER 893272 Export to MS Excel or CSV from Web is incomplete 888362 Helpful technical hints for installing and maintaining MIC 834077 rdisp/plugin_auto_logout overrides ICF timeout 737625 Parameter recommendations for the ICM 698017 ICM Patch Collection (6.40) 634006 Note on the preclarification of ICM messages 633539 Time-out problems in the IC WebClient This document is referenced by: SAP Notes (17) 893272 Export to MS Excel or CSV from Web is incomplete 1488594 PI CTC: Connection to system Integration Builder lost 906435 XI Internal HTTP Error during CALL_ADAPTER 1352731 MOpz: Download or deployment hangs when using SLM 834077 rdisp/plugin_auto_logout overrides ICF timeout 1432150 XI runtime: HTTP return code 110 921061 How to set Timeouts in Mobile Infrastructure 1811778 TIMEOUT of server port does not override global parameter icm/keep_alive_timeout 1162605 Network performance for CRM (IC) Webclient 737625 Parameter recommendations for the ICM 1004684 Abort of large content import and transport 888362 Helpful technical hints for installing and maintaining MIC 981211 HTTP debugging with the new debugger is terminated 633539 Time-out problems in the IC WebClient 1347276 IC_AGENT Business Role:Pre-mature closure of IE 1139406 CTS+: cx_ai_system_fault during import of orders 634006 Note on the preclarification of ICM messages .
Report "824554 - ICM and SAP Web Dispatcher Timeout Parameter.pdf"