Question:
Hi SAP Fans,
When running Web applications which takes longer than 60 secs to update, I recieve a connection timed out error from the WAS:
500 Connection timed out
Connection timed out (-5)
--------------------------------------------------------------------------------
Error: -5
Version: 6020
Component: ICM
Module: icxxthr_mt.c
Line: 2086
Server: ms1a01cs_BXT_00
Detail: Connection to partner timed out
The query runs fine when run with further restrictions. The job on the BW site does not time out. Any suggestions to how we can solve this problem is very much appreciated.
Cheers
Bonde
_________________
______________________________
Jorgen Bonde Rasmussen
jbrasmussen@mail.dk
Answer:
configure your WAS timeout period (default is 300).
Answer:
Guest,
Thanks for your quick reply. Can you point me to where this is done. I will then let the Basis team know straight away.
Thanks in advance.
Cheers
Bonde
_________________
______________________________
Jorgen Bonde Rasmussen
jbrasmussen@mail.dk
Answer:
Guest,
Thanks for your quick reply. Can you point me to where this is done. I will then let the Basis team know straight away.
Thanks in advance.
Cheers
Bonde
_________________
______________________________
Jorgen Bonde Rasmussen
jbrasmussen@mail.dk
Answer:
RZ10, it is a configuration parameter. Mind that a change here will require a re-start of SAP services to affect the change. Maintain the profile as Extended Maint. But your BASIS team should be aware of all of this already.
Specifically,
rdisp/keepalive
rdisp/gui_auto_logout
icm/keep_alive_timeout
icm/conn_timeout
There might be another. This is just off the top of my head.....
- Stephen
Answer:
Stephen,
Thank you for your reply. I checked all the system parameters and the four you mentioned seems to be the ones affecting the web timeouts (especially the icm/...). I have checked our system profile and they are not set. The system is therefore using defaults.
I have forwarded the information to basis and hope that this helps them solve the problem.
Cheers
Jorgen
_________________
______________________________
Jorgen Bonde Rasmussen
jbrasmussen@mail.dk
Answer:
... for web reporting in BW the defaults are not sufficient, especially when you have objects generating for the first time, or large running queries. It will probably take some playing to get to the right level.
Answer:
Hi,
I set the session timout period...but it changes back to its default the next days.
Answer:
Hi,
have a look at transaction SMICM then "goto" -> Services
there you will see your timeout intervall for Web-requests
You can maintain this in RZ10 - the parameters are for example:
icm/server_port_0 PROT=HTTP,PORT=8080,TIMEOUT=3600
icm/server_port_1 PROT=SMTP,PORT=25,TIMEOUT=3600
HTH, best regards,
Sascha
Answer:
Hi all,
Thank you for your feedback.
The problem has now been solved.
The system parameter 'icm/keep_alive_timeout' was set to default which was 60 sec. Unless you have a super optimized BW system, there will be queries running longer than this. After changing the parameter (RZ10), the queries runs ok.
Thanks for the help guys,
Cheers
Bonde
_________________
______________________________
Jorgen Bonde Rasmussen
jbrasmussen@mail.dk
Answer:
icm/server_port_0 PROT=HTTP,PORT=8080,TIMEOUT=3600
icm/server_port_1 PROT=SMTP,PORT=25,TIMEOUT=3600
Sascha,
Does this affect the behavior differently then setting the seperate variables I listed? Or is it the same? If so, which of the variables below would that TIMEOUT setting be equivalent to?
rdisp/keepalive
rdisp/gui_auto_logout
icm/keep_alive_timeout
icm/conn_timeout
Thanks,
- Stephen
Answer:
Hello Stephen,
I´ve asked our Web-specialist:
rdisp/keepalive is only valid for SAPGUI
rdisp/gui_auto_logout is only valid for SAPGUI
icm/keep_alive_timeout: default value, but if you specify icm_server_port value, this will be taken.
icm/conn_timeout : specifies, how long the system tries to setup a connection
hope this helps, best regards,
Sascha
Answer:
Sasha,
Yes, thank you for the clarification.
- Stephen