- How the need of session restart is detected
- How the session restart is implemented
- How Memory Threshold set in Technical profile is loaded by UI framework
- How to view session restart log
For each business role we can assign a technical profile to it.
Do you know the meaning of the Memory Threshold configured here?
If not, you can set a very low value to it for example 10MB, and go back to your system to observe the session restart behavior.
How the need of session restart is detected
Every time we switch among different work centers, the necessity of session restart is checked:
In handle_restart method, for Non-external navigation ( navigation between WebUI work centers ), BOL reset is by default considered as necessary – gv_bol_reset_requested is set as true in line 18.
Later on the navigation handling method this flag will be evaluated:
And the check about whether the current memory consumption has exceeded the threshold configured in technical profile is performed in line 23, method query_session_reset.
The check logic done in below method:
Once it is determined to restart the current session, a flag gv_restart_cause is set with corresponding reset reason.
How the session restart is implemented
Before restart, all current user data are stored via server side cookie.
When a new session is successfully launched, all previous stored information are now restored:
How Memory Threshold set in Technical profile is loaded by UI framework
This is pretty easy to find, in constructor of CL_CRM_UI_MEMORY_UTILS.
How to view session restart log
Activate log setting in tcode SAAB, log point id: BSP_WD_MEM_TRACE
After that once session restart and restore occurs, it will be recorded and displayed in SAAB: