Skip to main content

Support Article

Section execution error on page pyDisplayHarness

SA-38692

Summary



Access the user portal and keep it for idle, say for 10 minutes.

Post idle time, access any of the gadget button from the left hand side panel.

This gives the reported error:

Section 'MyDiaryDetails' execution error on page 'pyDisplayHarness' of class 'ABC-Data-UUser_Diary': Problem in JSP fragment.


Error Messages


Section 'MyDiaryDetails' execution error on page 'pyDisplayHarness' of class 'ABC-Data-UUser_Diary': Problem in JSP fragment.


Steps to Reproduce



1. Launch Case Worker portal.
2. Access any of the gadget button from left hand side panel.
3. Keep the page idle (say for 10 minutes).
4. Access any of the gadget button from left hand side panel.

Actual Behavior: Error message shown on the UI
Expected Behavior: UI related to the gadget to be shown to the user.

Root Cause



Logs reported below error only when page undergoes passivation and not always.

Caused by:
com.pega.pegarules.pub.PRRuntimeException: Exception in java property wrapper method.
at CASLExtUserEntitlement.prpcwrapper.UserEntitlementsRespType.prGetObject(UserEntitlementsRespType.java:193)
at com.pega.pegarules.data.internal.clipboard.ClipboardPageBase.getAttachedJavaObject(ClipboardPageBase.java:824)
at
java.lang.NullPointerException
at CASLExtUserEntitlement.UserEntitlementsRespType.getUserAppEntitlement(UserEntitlementsRespType.java:36)
at CASLExtUserEntitlement.prpcwrapper.UserEntitlementsRespType.prGetObject(UserEntitlementsRespType.java:183)
... 108 more


It was found that custom class is not serializable.

Resolution



Perform the local-change steps (increase passivation time via DSS setting) to resolve the issue:
  1. In prconfig.xml, change the value of, “initialization/PersistRequestor” to “Never”.
  2. To change the timeout to 1 hour, change the below values to “3600”.
  • timeout/thread
  • timeout/page
  • initialization/passivationinterval
As permanent solution, user is suggested to serialize all the custom classes using the below steps:

a) Re-run the wizard to regenerate the wrapper after making changes to custom bean classes.
b) Re-run the use-case.

Suggest Edit

Published July 6, 2017 - Updated October 8, 2020

Did you find this content helpful?

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.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us