pyWorkPage is getting removed from clipboard after inactivity of 20 to 30 minutes in 8.6
Hello Team,
The scenario is as below:
In my application, we create one work object (first screen) and on click of a button next screen will be visible where a different WO gets created. (No parent child relation between them).
After upgrade from V7 to 8.6 we observed that when we are creating the first case (1st WO gets created) and now if we keep that wo idle for 20-30 minutes and when we click on button to go to next screen, we are getting null pointer exception and the pyWorkPage of that WO is also getting removed from the clipboard.
Can anyone please help me with this situation?
We are not getting any timeout error. We are getting java.lang.nullpointer exception.
Thanks,
Taniya
***Edited by Moderator Marije to add Update and Capability tags***
Bits In Glass
GB
@TaniyaD3 Hi Taniya, This happens when the passivation occurs, look for passivation
What is the scenario to keep the user to remain in the same screen for 20-30 minutes? The null pointer exception happens if the flow name or any connector references are not found on submit (newassignpage)
Can you look into the trace and logs, it will help debug the issue.
TCS
AE
Thank you so much for quick response.
I know the place in flow, it is showing null pointer exception for one connector but why it is happening in 8.6?
In V7.4 it used to work fine.
And is there any way to resolve it?
But I do not see any timeout error in log.
Thanks,
Taniya
TCS
AE
Is there any way to resolve this?
We need that user should able to continue working after inactivity of 30 minutes.
Thanks,
Taniya
Updated: 20 May 2022 6:57 EDT
Pegasystems Inc.
GB
@TaniyaD3 please could you check the deprecated functionality in 8.4 and configure pyPostActivation as per the Configuring your system for passivation and activation documentation?
Please also go through the Session Management Troubleshooting FAQs 8.4 configuration parameters recommended in our documentation Defining passivation storage
Note that some passivation issues were resolved in 8.4 See the Resolved Issues documentation.
Bits In Glass
GB
Have a look at this
TCS
AE
I went through the link but somehow I think my passivated page is not getting activated.
I have below DSS in my application:
initialization/persisrequestor/default : OnTimeout
initialization/persistrequestor/storage/default : filesystem
initialization/persisrequestor/usepagelevelpassivation : true
For this DSS, from one article I came to know that pega had suggested not to touch this DSS and it is deprecated and have no role in passivation anymore.
session/ha/quiesce/passivationTimeout : 5
prconfig/timeout/browser/default : 1800
So we need passivation in my application and above are the DSS setting. And we want that user to continue work after inactivity of 30 minutes.
But I am not sure what extra setting we need to do to avoid null pointer exception.
Thanks in advance!
Taniya
Pegasystems Inc.
GB
@TaniyaD3 I believe it might be best if you log this as a Support Incident.
Please provide the INC ticket reference here so that we can help track progress on the investigation.
Bits In Glass
GB
@TaniyaD3 Can you provide a Trace/ Log so that it would be easier to identify which part of the application is causing the null pointer exception?
Example: If a Parameterised Data page is causing the issue, it can be configured to refresh every 30 minutes.