Question
U.S. Department of Justice
US
Last activity: 11 Sep 2018 23:17 EDT
Pega 7.4 Unable to passivate page issue noticed in the log file.
2018-09-11 09:11:46,767 [ES PassivationDaemon] [ STANDARD] [ ] [ ] ( mgmt.base.NodeRequestorMgt) ERROR - Unable to timeout page. No data has been lost at this time. As a best practice, ensure all properties are Serializable to protect against data loss.;com.pega.pegarules.session.external.mgmt.PageCannotBeSerializedForPassivationException: Unable to passivate page 'pyWorkPage' on thread 'STANDARD' in requestor 'HCBUJJL1X2COVG5X9EFLQ4UNF786IXAQM'.
2018-09-11 09:11:46,767 [ES PassivationDaemon] [ STANDARD] [ ] [ ] ( mgmt.base.NodeRequestorMgt) ERROR - Unable to timeout page. No data has been lost at this time. As a best practice, ensure all properties are Serializable to protect against data loss.;com.pega.pegarules.session.external.mgmt.PageCannotBeSerializedForPassivationException: Unable to passivate page 'pyWorkPage' on thread 'STANDARD' in requestor 'HCBUJJL1X2COVG5X9EFLQ4UNF786IXAQM'. The following items were not serializable: [Property not serializable: "pyWorkPage.pyParseState" Class: "com.pega.pegarules.integration.engine.internal.mapping.ParseStateImpl"].; at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.getPageAsBytes(NodeRequestorMgt.java:3591) ~[prprivate.jar:?]; at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.getPageAsBytes(NodeRequestorMgt.java:3545) ~[prprivate.jar:?]; at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.savePage(NodeRequestorMgt.java:974) ~[prprivate.jar:?]; at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.processPassivationQueue(NodeRequestorMgt.java:2846) ~[prprivate.jar:?]; at com.pega.pegarules.session.internal.async.PassivationDaemon.processPassivationQueue(PassivationDaemon.java:367) ~[prprivate.jar:?]; at com.pega.pegarules.session.internal.async.PassivationDaemon.run(PassivationDaemon.java:341) ~[prprivate.jar:?]; at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1357) ~[prprivate.jar:?]; at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1105) ~[prprivate.jar:?]; at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:912) ~[prprivate.jar:?]; at com.pega.pegarules.session.internal.async.PassivationDaemon.run(PassivationDaemon.java:303) ~[prprivate.jar:?]; at java.lang.Thread.run(Thread.java:785) [?:1.8.0-internal];
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
US
Hi Mohamed,
There are few known issues on PageCannotBeSerializedForPassivationException depending on the version and some patches have been provided.
I could see that exception occured on PassivationDaemon process while saving certain pages for passivation.
If the exception is blocking something or If it's frequently occurring in log files, I would recommend you to create one SR with Pega Support and get it investigated to come up with a conclusion.
Thank you!