500 Connection timed out

[Former Member]

Hi,

I am getting a time-out dump in my WD application (Non-interactive adobe form output).

right now timeout parameter is 60 sec.How do we increase this timeout in portal? Is it a best practice to increase the time-out parameter.

Error: -5 
Version: 7000 
Component: ICM 
Date/Time: Tue Apr 28 09:46:05 2009  
Module: icxxthr.c 
Line: 2698 
Server: sape-dev_DV1_00 
Error Tag: {-} 
Detail: Connection to partner timed out after 60s

If not How do we do performance tuning in WD application?Looks like

my select statements and loops are taking a bit longer than 60 secs and I have directly placed code in WD Application method.

How should we overcome these kind of issues?

rgds

Vara

Edited by: Vara K on Apr 28, 2009 4:57 PM

[Former Member]

Hey!

You can increase the parameter of time. But general case, you need not change.

If you want to change, you can use transaction code RZ11 to change profile parameters 'ms/http_timeout'.

ms/http_timeout

Short description(Engl)   Timeout for HTTP and HTTPS requests
Appl. area                Message server
ParameterTyp              Time value
Changes allowed           Change permitted
Valid for oper. system    All operating systems
Minimum                   1
Maximum                   600
DynamicallySwitchable
Same on all servers

Dflt value                20
ProfileVal                20
Current value             20

[Former Member]

Thank you both for the info.

I am just curious what would be general timeout settings from portal side?

reason is it is just 60 sec on our site.

Rgds

Vara

Edited by: Vara K on Apr 29, 2009 8:21 PM

[thomas_jung]

There is no clear cut right or wrong answer to what you conneciton time out should be. It is always a ballance of resources vs. optimization of your code. You Basis team can use profile parameters to increase this time, but it might not be the best approach.

You can use all the normal ABAP monitoring tools (performance trace, SQL trace, etc) to track down where you are having performance problems in your Web Dynpro ABAP application.

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/73ee80347e0e27e10000000a421937/frameset.htm

Once you know more about the source of the problem perhaps we can make a suggestion here to help you. Also it would be helpful to know a little bit about your application - what does it do, how much data does it display, etc.