icm/keep_alive_timeout parameter

[Former Member]

Hi All

I posted the thread below yesterday on the BI related forums with no responses so am hoping one of you ABAP'ers may know about the icm/keep_alive_timeout parameter...

We have a number of BW Reports that one day run on BWQ client in 2 minutes and the next day (after no changes have been made) it will time out after 300 seconds. On the day it times out, if we check transaction SM66 the report job is still running in the background. Our Basis Team suggest this might be caused by memory usage on the application server. We've run the report through RSRT and it looks OK - no red lights so no performance issues ...?

Our Basis Team have changed parameter

icm/keep_alive_timeout to -1 in transaction RZ11 in BW that I understand should solve the timeout error and they have restarted the system. However, the same report is still timing out after 300 seconds do we need to change RZ10 or RZ11 on the R3 side as well?

Does anyone have any thoughts / suggestions?

Thank you in advance.

Helen

[Former Member]

Hi Helen,

There are a number of parameters on R/3 side related to timeout.

abap/timeout

em/stat_log_timeout

enque/con_timeout

enque/snapshot_timeout

gw/cpic_timeout

gw/deallocate_timeout

gw/gwwp_connect_timeout

gw/internal_timeout

gw/reg_timeout

gw/resolve_timeout

gw/timeout

icm/conn_timeout

icm/keep_alive_timeout

icm/wp_roll_timeout

mdm/network_timeout

ms/conn_timeout

ms/http_timeout

ms/timeout

net/timeout

rdisp/async_dialog_timeout

rdisp/j2ee_timeout

rdisp/jvm_pool_timeout

rdisp/keepalive_timeout

rdisp/ms_keepalive_timeout

rdisp/plugin_pool_timeout

rdisp/rfc_pool_timeout

rdisp/softcancel_timeout

rspo/tcp/timeout/connect

rspo/tcp/timeout/read

rspo/tcp/timeout/write

You can ask your BASIS team to run through these from RZ11 and check which one has a value of 300 seconds set.

This could be the cause of the premature dump and corrected.

Cheers,

Aditya

[Former Member]

Thanks for that Aditya, very helpful - have awarded points.

Not sure about this as it's not my area of knowledge but would you know whether these are just general time out parameters or would any of them relate just to the BW environment??

Thanks again in advance

Helen

[Former Member]

Hi Helen,

I am not sure how far the BW interacts with R/3. I would assume if the time out was occuring during upload of data from R/3 into BW, then a parameter like abap\timeout would come into play which decides how much time an ABAP program can run in foreground without timing out.

However, about BW end, not sure, hence just felt to eliminate the danger from R/3 end, you can check with BASIS to find any of the below parameters which have 300 seconds, change it, retest the BW report.

Worst case, it wont have any different, and best case, we would identify the issue, realize there is an integration there.

Regards,

Aditya

[Former Member]

Thanks once again Aditya. If the change we've made doesn't help we'll ask Basis to look at the other parameters you mention.

Regards

Helen