On hold/Priv dialog work process not ending after AS timeout expiration

[benoit-schmid]

Hello,

This morning, there was a Dialog Work Process in mod On Hold / Priv.

The Runtime reported in sm50 was more than 18 hours.

The report name in sm50 was SAPLSMTR_NAVIGATION.

The last transaction (FS10N) in the audit log for this user dated for more than two days ago.

The user told me that he did not restart a new transaction since the day before.

The following parameters are set in our system:

rdisp/max_wprun_time = 6000

rdisp/gui_auto_logout   = 9000

Could you explain me why this user was not auto logged out?

Naively I thought that after 1.66 hour a working transaction would end.

Then after 2.5 hour there would be an automatic logout.

But I misunderstand these timeouts behaviors.

Thanks in advance for your answers.

[Former Member · Accepted solution]

Hello,

If any workprocess gtes in PRiV mode then the mentioned timeout parameters will not  applicable. The WP will continue to run till the assigned operation is completed.

You can limit the no. of PRIV mode workprocesses with the parameter rdisp/wppriv_max_no.

More info can be checked on the link :

http://help.sap.com/saphelp_nw04s/helpdata/en/7a/caa6f3bfdb11d188b30000e83539c3/content.htm

Hope it clarifies your query.

Regards,

Mudasir.

[benoit-schmid · Accepted solution]

Hello,

The help you have provided explains clearly how the WAS behaves with PRIV Mode work processes.

Do you know why SAP has decided to deactivate the classical max_wprun_time and gui_auto_logout

behavior in case of PRIV mode?

When the trigger linked to max_priv_time is reached, does the work process

go back in non PRIV mode?

Thanks in advance for your answers.

[Former Member · Accepted solution]

Hi,

Do you know why SAP has decided to deactivate the classical max_wprun_time and gui_auto_logout

behavior in case of PRIV mode?

A :  It depends on the SAP designed behavior and it provides flexibility incase few operations needs more processing time or memory to complete the task.

When the trigger linked to max_priv_time is reached, does the work process go back in non PRIV mode?

A :As mentioned in SAP help, the oldest Priv WP is reset ( in other words.. terminated ).

Extract from the link :

" To determine this number n, set the value of the profile parameter rdisp/wppriv_max_no. If a value is not entered, the SAP System determines this number using the following formula:

the number (n) is set to the greater of the 2 following values:

    Number of dialog work processes minus 5

    1

If more than ('n' derived from rdisp/wppriv_max_no ) dialog work processes are active and the time span set in parameter rdisp/max_priv_time (default 600 seconds) has elapsed, the transaction for that PRIV process, which has spent the longest possible time in PRIV mode, is reset."

Hope it clarifies.  You may close the thread if your query has been answered.

Regards,

Mudasir.

[joe_ledesma · Accepted solution]

In case anyone finds this old post as I did, here is an updated SAP Help link:

http://help.sap.com/saphelp_erp60_sp/helpdata/en/7a/caa6f3bfdb11d188b30000e83539c3/frameset.htm

[former_member188883]

Hi Benoit,

The report name in sm50 was SAPLSMTR_NAVIGATION

This report can be seen only when user session is disconnected due to some network problems but the same has not been reflected into SM50.

Auto logout parameters do not have an impact in such situations. You need to manally kill these sessions.

Regards,

Deepak Kori

[former_member188883]

Hi Benoit,

Additionally you may refer following SAP notes.

Note 569587 - High response times for Session Manager in ST03

Note 203617 - High memory consumption with Easy Access menu

Regards,

Deepak Kori