timeout

[Former Member]

We have

icm/keep_alive_timeout 7200

rdisp/plugin_auto_logout 43200

icm/server_port_0 PROT=HTTP,PORT=80$$

Two questions

1) Will inactivity of more than 7200 sec cause me a time out and the session to be terminated ? Or because my plugin_auto_logout is 12 hrs .. I can reconnect without having to login again ?

2) We have not set PROCTIMEOUT and so per the link below what will be my PROCTIMEOUT ? 30 sec or 7200 sec ?

http://help.sap.com/saphelp_nw2004s/helpdata/en/0b/1c7e7abbc311d5993a00508b6b8b11/content.htm

thank you

regards

Laxmi

[alen_mikulic]

Answers in bold as per the sap help.

1) Will inactivity of more than 7200 sec cause me a time out and the session to be terminated ? Or because my plugin_auto_logout is 12 hrs .. I can reconnect without having to login again ?

Yes you have to login again but your user context should be available to as the logout is higher.

2) We have not set PROCTIMEOUT and so per the link below what will be my PROCTIMEOUT ? 30 sec or 7200 sec ?

http://help.sap.com/saphelp_nw2004s/helpdata/en/0b/1c7e7abbc311d5993a00508b6b8b11/content.htm

30 sec , as it defaults to this if parameter not specified.

[Former Member]

Thank you Sam.

I tested this and I dont need to login again after an inactivty of 7200 sec. I thought I would have to but I didnt. Also each time I leave and login back into the CRM system I see a new user context getting created. I see a new entry in sm04 with the latest time timstamp. And the old user context just stays holding memory until the plugin time out when it is kicked out.

Is this a bug and has any one seen this behavior ?

[Former Member]

Both the icm/keep_alive_timeout and rdisp/plugin_auto_logout are both inactivity timeout parameters that cleanup different parts of your http connection. It would make sense to have these set to the same value so that both are cleaned up after a specific time of no activity. Why have 2 parameters to do monitor inactivity is the mystery.

The PROCTIMEOUT parameter is for the backend ABAP processing of the http request. The default is 30 seconds, so if the ABAP report/function hasn't processed the request in this time you get a timeout. You get alot of PROCTIMEOUTs after you apply Service Packs because the time taken for the ABAP regenerations means your request takes longer to get processed than normal. It's not related to the 2 parameters above.

Regards

Doug.

[Former Member]

Thank You Doug.

It looks like the the definition of proc time matches very close to the max_wprun_time , the time a process runs on the wp.

Is there some relation to these two ? How must they be set wrt one another ? We have max_wprun_time as 6000 sec.

thank you

[Former Member]

The PROCTIMEOUT I described above (ABAP backend processing) is exactly like the max_wprun_time profile parameter. However, HTTP plugin + also communicates with other HTTP services (eg portals,CRM etc).

So they are slightly different, PROCTIMEOUT is for ICM ABAP an HTTP communications while max_wprun_time is only for ABAP.

Regards

Doug

[Former Member]

thank you Doug. Points awarded.

Closing thread.