500 Connection timed out

Question

Hello,
I receive a 500 Connection timed out error.
I know that there are some threads to this error but I can´t find a solution for us.
This is the error description:
Error:            -5
Version:        7000
Component:  ICM
Date/Time:    Tue Mar 04 07:02:38 2008
Module:        icxxthr.c
Line:             2698
Server:         crmprod_CRP_01
Error Tag:     {-}
Detail:          Connection to partner timed out after 60s
Now I have found in this forum some information about the parameters icm/keep_alive_timeout, icm/conn_timeout and icm/server_port_*
Our settings for this parameters are:
icm/server_port_0 = PROT=HTTP,PORT=8001
icm/server_port_1 = PROT=SMTP,PORT=25
icm/keep_alive_timeout (sec.) = 600
icm/conn_timeout (msec.) = 5000
Can someone please explain me which parameters occurs this error and which parameters I can change that the connection time is longer than 60 seconds?
Where can I change the parameters?
Regards
Philipp

Answer 1

Hi,
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".
Therefore, exceeding the icm/conn_timeout does not lead to a "500 Connection timed out" error message.
Processing timeout and keepalive timeout
The icm/keep_alive_timeout and icm/server_port_< n > parameters define the keepalive timeout and the processing timeout.
ICM distinguishes between these two types of timeout.
The processing timeout is the timeout between the HTTP request being issued and the HTTP response being received.
If the ICM is used as a server for the relevant HTTP request (in other words, when it forwards an incoming request to the SAP Web Application Server), the processing timeout is the time that the ICM will wait until a response is received from the SAP Web Application Server (ABAP or J2EE). This interval may be exceeded with long-running applications in ABAP or the J2EE engine. If the processing timeouts are 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 Web Application Server), the processing timeout is the 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.
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.
Configuration of the ICM parameters for the processing timeout and the keepalive timeout
For the ICM, the parameters mentioned here are in the instance profile.
The processing timeout is set for individual services with the following parameter:
icm/server_port_ < n > = ...,PROCTIMEOUT=< s >.
The keepalive timeout can be set globally for all services of the ICM with the parameter icm/keepalive_timeout.
You can also set it for individual services by using the following parameter:
icm/server_port_ < n > = ...,TIMEOUT=< s >.
  If you set this parameter, it overwrites parameter icm/keepalive_timeout for the specified service.
Even if the ICM serves as client for a request, the TIMEOUT and PROCTIMEOUT parameters of icm/server_port_ < n > control the timeouts for the relevant protocol, provided that you have set TIMEOUT or PROCTIMEOUT.
If you have not set the PROCTIMEOUT parameter, TIMEOUT (or icm/keepalive_timeout) defines both the processing timeout and the keepalive timeout. Also, as of release 6.40, the keepalive timeout is limited to a maximum of 30 seconds.
In a system where the default timeout settings of 30 seconds for the keepalive timeout and the processing timeout are not sufficient because of long-running applications, we recommend that you set the TIMEOUT and PROCTIMEOUT parameters for the relevant services so that you can configure them independently of each other. In addition, we recommend that you do not set the TIMEOUT value higher than necessary, for example, to the usual default value of 30 seconds.
We recommend, for example, the following settings:
icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600
to allow a maximum processing time of 10 minutes.
I hope this info will help you to sort out the error you getting.
Regards
Aashish Sinha
PS : reward points if helpful