500 Connection timed out

[former_member325638]

Hi Experts,

Few users who are accessing SA via portal and not via GUI are facing time out issue for particular sales > Trade spend application. While same is working for those who have SAP logon oad and is logging in via that. The error message is shown below:

500 Connection Timed out

Error -5

Version 7000

Component ICM

Module icxxthr.c

Line 2698

Server ---

Error tag {-}

Details : Connection to partner timed out after 60 seconds

Following are few related parameters with their current values in out ECC system:

rdisp/gui_auto_logout 7200

icm/keep_alive_timeout 90

rdisp/gui_auto_logout 7200

rdisp/plugin_auto_logout 1800

In SM21; it shows error:

HTTP/RFC session has been deleted following timeout

Run-time error "TIME_OUT" occurred

> Short dump "110426 105848 " created

This is in ECC system with basis level SAPKB70021>

It appears parameters are correct and also those who login and access this sales application via loggin in with logon pad do not face this proble. Only those who use SAP via portal are facing this issue

[Former Member · Accepted solution]

Hi Varun,

In SAP we can change the HTTP parameter value dynamically.

Please execute the transaction SMICM and go to services in menu tab and change the value of HTTP to 3600 and let me know if still facing the issue.

To fix the issue permanetly set the following parameter icm/server_port_0= PROT=HTTP,PORT=80$$,TIMEOUT=3000,PROCTIMEOUT=3600 and restart the system.

Thanks &Regards,

Devender

Edited by: Mella.Devender on May 4, 2011 3:27 PM

[former_member325638 · Accepted solution]

Thanks a lot Devender. Need some more guidance form you

Current value in SMICM is below:

No. Protocol Service Name/Port Host Name Keep Alive Proc.Timeo Actv External Bind

1 HTTP 8000 usushapspv196. 30 90

2 SMTP 0 usushapspv196 30 90

Should I change keep alive time or max processing time. Also there are 10 app servers with hload balancing. Should I do it on all of those as user can go to any of those via load balancing.

Please advise.

Thanks

[Former Member · Accepted solution]

Hi,

Setting the ICM PROCTIMEOUT value to 3600 (1 hour !) is, in my opinion, a very bad idea : it is much too long.

You will keep too much unactive connections, and so consume too much resources.

It is logical to choose a value just slightly longer than the ABAP time out rdisp/max_wprun_time.

In my systems, rdisp/max_wprun_time is set to 600 s (10 minutes) and the ICM PROCTIMEOUT is set to 620 seconds.

PS : Of course the Portal time out has to be longer than the ICM abap PROCTIMEOUT...

Regards,

Olivier

[sivakumar_kilari3]

> Details : Connection to partner timed out after 60 seconds

Change this parameter value icm/keep_alive_timeout by default 60 seconds.

Thanks

Siva

[former_member325638]

Hi Siva,

ICM Keep alive time out is 90 seconds as mentioned aboce

[Former Member]

Hello Varun,

Again the users are connecting to your ABAP system using portal as front end.

If ICM has all settings fine then if the user session is timing out after 10 minuts its standard.

As the query being executed exceed the maximum dialogue workjprocess runtime the transaction will time out.

Try to get information on what user is trying to do on the system and all HTTP sessions connect to ABAP using dialogue workprocess.

If its for a short duration till they process that part of the transaction you can increase the dialogie work process time out to higher values rdisp/max_wprun_time. This parameter is always 600 as standard.

Regards

Vivek

[Former Member]

Hi,

Check your ICM timeout parameters :

icm/server_port : values for TIMEOUT and PROCTIMEOUT

Most probably the problem comes from a value too small for PROCTIMEOUT.

Regards,

Olivier

[former_member325638]

Hi Oliver,

Could you please update how can i verify PROCTIMEOUT . There is no profile parameter named as PROCTIMEOUT in profile parameters.

The valuew of ICM server port is

icm/server_port_0 = PROT=HTTP,PORT=8000

Thanks,

Varun