Session hangs after timeout
When the session is left idle so that it reaches the timeout time, it starts behaving weirdly. When trying to add a new row to a row repeat, the session is hanging and the user cannot take any action. The user has to close the browser window and relogin.
IE Error or the session is hung.
Steps to Reproduce
- Login to system.
- Go to a screen where there is a repeat grid present.
- Let the system be idle at that screen, so that it reaches the max timeout.
- Once the timeout time is reached try to add a row to the repeat grid.
- Session is either getting hung or showing an IE error. Whereas it should redirect the user to a login screen.
The root cause of this problem is a defect in customer application code/rules.
The PRPC User Interface can not handle the Siteminder Idle Timeout HTML. When we make an AJAX call for something like reloadSection and a Siteminder idle timeout has occured, the response is not coming from PRPC, it comes from Siteminder. The proper way to avoid this issue is to use the pxSessionTimer.
When building a end user harness it should contian a panel set so that it properly implements the pega desktop api logic. Only the pega desktop api can use the pxSessionTimer.
This issue is resolved by making the following change to the PRPC operating environment:
The end user portals should contain a panel set so the pega desktop api is added. Only by modifying the end user portals to include the panel set can the pxSessionTimer be used and these problems be avoided..
Published December 15, 2016 - Updated October 8, 2020
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.