Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Danny Cheung (dannyc21)
Facebook
Product Management
Facebook
US
dannyc21 Member since 2016 11 posts
Facebook
Posted: Jan 22, 2017
Last activity: Feb 21, 2017
Posted: 22 Jan 2017 23:55 EST
Last activity: 21 Feb 2017 1:04 EST
Closed
Solved

PageCannotBeSerializedForPassivationException: Unable to passivate page 'pyCorrList'

Keep getting this error in Pega Logs. Most likely come from this OOTB activity we are using ListOfValidCorrs

Please, help me understand how to get rid of this error.

Show More

Keep getting this error in Pega Logs. Most likely come from this OOTB activity we are using ListOfValidCorrs

Please, help me understand how to get rid of this error.

2017-01-22 20:08:55,542 [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 'pyCorrList' on thread 'TABTHREAD3' in requestor 'H233C9547C3971B7953EE9D31CAA7C1C2'. The following items were not serializable: [Property not serializable: "pyCorrList.pxResults(1).else" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(1).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(3).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(4).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(5).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(6).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(7).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(10).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(11).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(12).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(13).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(14).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(15).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(16).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(17).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(18).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(19).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(20).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(21).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(22).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(23).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(24).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(25).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl", Property not serializable: "pyCorrList.pxResults(27).pyRelativePath" Class: "com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl" Problem class: "com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl"]. 
	at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.getPageAsBytes(NodeRequestorMgt.java:3449) 
	at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.getPageAsBytes(NodeRequestorMgt.java:3403) 
	at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.savePage(NodeRequestorMgt.java:944) 
	at com.pega.pegarules.session.internal.mgmt.base.NodeRequestorMgt.processPassivationQueue(NodeRequestorMgt.java:2712) 
	at com.pega.pegarules.session.internal.async.PassivationDaemon.processPassivationQueue(PassivationDaemon.java:365) 
	at com.pega.pegarules.session.internal.async.PassivationDaemon.run(PassivationDaemon.java:339) 
	at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1290) 
	at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1038) 
	at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:847) 
	at com.pega.pegarules.session.internal.async.PassivationDaemon.run(PassivationDaemon.java:301) 
	at java.lang.Thread.run(Thread.java:745)

***Moderator Edit: Vidyaranjan| Updated Categories***


Show Less
To see attachments, please log in.
System Administration

Accepted Solution

Posted: 7 years ago
Posted: 24 Jan 2017 4:30 EST
Mohammad Asif Hasan (Mohammad_Asif_Hasan)
EPAM Systems, Inc.
Mohammad Asif Hasan
EPAM Systems, Inc.
ES

Hi Danny,

Page passivation is used to improve system performance by removing pages from the clipboard that have not been accessed by a requestor for a specified period of time. Other pages for that requestor remain in memory, and requestor processing continues normally until that page is needed (such as for read access or for update) and is reactivated into memory.

Similarly, when an entire thread or requestor is inactive, the thread context or requestor context can be passivated (including the associated clipboard pages).

Passivation uses Java serialization when persisting clipboard pages to storage. Two options are used during this process: serialization (encoding) and deserialization (decoding) of data.

By default, the passivation daemon, which operates once per minute, passivates the following:

Show More

Hi Danny,

Page passivation is used to improve system performance by removing pages from the clipboard that have not been accessed by a requestor for a specified period of time. Other pages for that requestor remain in memory, and requestor processing continues normally until that page is needed (such as for read access or for update) and is reactivated into memory.

Similarly, when an entire thread or requestor is inactive, the thread context or requestor context can be passivated (including the associated clipboard pages).

Passivation uses Java serialization when persisting clipboard pages to storage. Two options are used during this process: serialization (encoding) and deserialization (decoding) of data.

By default, the passivation daemon, which operates once per minute, passivates the following:

  • Pages that are idle for at least 15 minutes
  • Threads that are idle for at least 30 minutes
  • Requestors that are idle for at least 60 minutes.

Refer this link to configure timeout passivation at your end :- https://community.pega.com/sites/default/files/help_v722/procomhelpmain.htm

I have noticed that for Pega 7.2, there is already a bug reported with similar error message, Could you confirm your version? 

SA :- https://community.pega.com/support/support-articles/error-during-requestor-page-passivation

I am not sure about How to implement serializable in Pega, I will research more and update you if I find anything relevant.

Kindly notify,if it helps.

Regards,

Asif


Show Less
To see attachments, please log in.

Accepted Solution

Posted: 7 years ago
Posted: 24 Jan 2017 4:30 EST
Mohammad Asif Hasan (Mohammad_Asif_Hasan)
EPAM Systems, Inc.
Mohammad Asif Hasan
EPAM Systems, Inc.
ES

Hi Danny,

Page passivation is used to improve system performance by removing pages from the clipboard that have not been accessed by a requestor for a specified period of time. Other pages for that requestor remain in memory, and requestor processing continues normally until that page is needed (such as for read access or for update) and is reactivated into memory.

Similarly, when an entire thread or requestor is inactive, the thread context or requestor context can be passivated (including the associated clipboard pages).

Passivation uses Java serialization when persisting clipboard pages to storage. Two options are used during this process: serialization (encoding) and deserialization (decoding) of data.

By default, the passivation daemon, which operates once per minute, passivates the following:

Show More

Hi Danny,

Page passivation is used to improve system performance by removing pages from the clipboard that have not been accessed by a requestor for a specified period of time. Other pages for that requestor remain in memory, and requestor processing continues normally until that page is needed (such as for read access or for update) and is reactivated into memory.

Similarly, when an entire thread or requestor is inactive, the thread context or requestor context can be passivated (including the associated clipboard pages).

Passivation uses Java serialization when persisting clipboard pages to storage. Two options are used during this process: serialization (encoding) and deserialization (decoding) of data.

By default, the passivation daemon, which operates once per minute, passivates the following:

  • Pages that are idle for at least 15 minutes
  • Threads that are idle for at least 30 minutes
  • Requestors that are idle for at least 60 minutes.

Refer this link to configure timeout passivation at your end :- https://community.pega.com/sites/default/files/help_v722/procomhelpmain.htm

I have noticed that for Pega 7.2, there is already a bug reported with similar error message, Could you confirm your version? 

SA :- https://community.pega.com/support/support-articles/error-during-requestor-page-passivation

I am not sure about How to implement serializable in Pega, I will research more and update you if I find anything relevant.

Kindly notify,if it helps.

Regards,

Asif


Show Less
To see attachments, please log in.

Related content:

Question

Unable to passivate page

Question

Modifying Page Passivation

Question Solved

Error Unable to passivate page 'Unable to passivate page 'pxRequestor' on thread 'null' in production logs

Question Solved

PageCannotBeSerializedForPassivationException: Unable to passivate page - Happens Only In Production and not in lower environment

Question

Pega 7.4 Unable to passivate page issue noticed in the log file.

Question Solved

Page Passivation - How do we configure time idle time for Page passivation.

Question

Unable to restore passivated requestor; error in authorization activation

Question

Pega 7.3 Unable to passivate page issue noticed in the log file.

Question

Passivation error

Question

Unable to passivate page 'RequestorTemp' on thread 'STANDARD' in requestor 'HXXXXXXXXDGJS0BU8D3Z8OAS'

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

Pega Collaboration Center 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