Parameter rdisp/keepalive_timeout recommendations

[Former Member]

Hi All,

We are facing issue of automatic GUI timeout for few Users:

• ERROR => DpCheckTerminals: NiCheck2(rc=-23) failed for tid: 432 (60secs)-> disconnecting [dpxxdisp.c 13296]

OSS Note 1109311 suggests to set paramtere rdisp/keepalive_timeout to overcome this issue.

Currently this parameter is at default value 60 sec. SAP default setting says we can set this parameter upto 5 min but I want to know What value we can consider at max for this parameter to avoid any system issue.

Shivam

Edited by: Shivam Mittal on Jan 10, 2012 8:29 PM

[former_member524429 · Accepted solution]

Hi,

Currently this parameter is at default value 60 sec. SAP default setting says we can set this parameter upto 5 min but I want to know What value we can consider at max for this parameter to avoid any system issue.

Whats value of other parameter rdisp/gui_auto_logout ?

I would recommend you to keep this parameter rdisp/keepalive_timeout with default value (which is 60 seconds). Already at every 1200 seconds (if rdisp/keepalive=1200), SAP dispatcher pings to those connections who are idle since 1200 seconds and not showing any data transfers. After sending such ping message, dispatcher will wait for the response from those connections until 60 seconds (if rdisp/keepalive_timeout =60). (so total time is 1200+60 = 1260 seconds in this case). If Dispatcher does not receive any response within this duration it terminates those connections and the same will be reflected at User side.

Please check the connection link between the Users console (SAP Gui) and the Server (Server's Netwrok) using niping tool (refer SAP Note 500235). Check weather its showing any packet drops/ doubtful TTL between these two points or not ? such factors may cause frequent Connection breakups. You can coordinate with you Network Operation Team for such link testing.

Regards,

Bhavik G. Shroff

[Former Member · Accepted solution]

Hi Bhavik,

Thanks for your suggestation.

But I just have one query on your reply:

So in my case duration 1260 Sec is max duration when any ideal connection can be active in my system but You said

"SAP dispatcher pings to those connections who are idle since 1200 seconds and not showing any data transfers".

So my question is when dispatcher checks for Ideal connection, Does it check for all Ideal sessions or only for sessions which are ideal since last 1200 secs only.

Beacuse if it is checking for all ideal connection then there can be some connections which are ideal since less time.

Regards,

Shivam

[former_member524429 · Accepted solution]

Hi,

when dispatcher checks for Ideal connection 

Dispatcher checks for idle GUI connections based on the specified duration (seconds) in parameter rdisp/keepalive.

 Does it check for all Ideal sessions or only for sessions which are ideal since last 1200 secs only.

if rdisp/keepalive is set with value 1200 seconds, then every after 1200 seconds dispatcher of SAP instance will check all those IDLE GUI connections/sessions which have not shown any kind of data transfers within 1200 seconds span of time. For such identified IDLE GUI connections, Dispatcher will send message (ping) and will wait until the duration specified in parameter rdisp/keepalive_timeout. After that, If Dispatcher will terminate all the IDLE GUI connections & Unacknowledged connections for which it has not received any responses within the duration specified in paramater rdisp/keepalive_timeout.

So ultimately the Dispatcher will terminate all the IDLE connections which have not shown any data transfers within the duration of rdisp/keepalive + rdisp/keepalive_timeout. (e.g. 1200 + 60 = 1260)

I hope the above information will be helpful.

Regards,

Bhavik G. Shroff

[tilo-sap]

fyi, for SAP VM running on Azure you need to tune this: (Azure VM TCP timeout default of 4min, so AZ closes your SAP GUI connection. )

https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/sap-gui-connection-closed-whe...

[former_member188883]

Hi Shivam,

As per practical experience I would suggest to keep the parameter value to 180 secs.

Regards,

Deepak Kori