Support Article
Passivation errors in PegaRULES log file
SA-56913
Summary
Passivation errors display in the PegaRULES log. The errors display after setting up Pega application on multiple nodes in a high-availability configuration. In this configuration all the nodes passivate the requestors in a single shared folder, and the database is not used as the passivation destination.
Error Messages
Agent Pega-RulesEngine #7: Code-.pzNodeCleaner encountered an execution error. Restarting after delay. Exception at 20180117T050003.794 GMT: com.pega.pegarules.pub.PRRuntimeException:
/path/more_paths/W9CE75743C4DD0A32686292E65423546A/metadata.ser (No such file or directory)
at com.pega.pegarules.pub.util.PRInputStream.getInputStream(PRInputStream.java:120)
at com.pega.pegarules.pub.util.PRInputStream.<init>(PRInputStream.java:101)
atcom.pega.pegarules.session.internal.mgmt.base.FilesystemStorage$RegularIO.readObjectFromInputStream(FilesystemStorage.java:961)atcom.pega.pegarules.session.internal.mgmt.base.FilesystemStorage$RegularIO.readFromDisk(FilesystemStorage.java:950)
at com.pega.pegarules.session.internal.mgmt.base.FilesystemStorage.getMetadata(FilesystemStorage.java:1195)
atcom.pega.pegarules.session.internal.mgmt.base.FilesystemStorage.deleteExpiredRequestorsDirectories(FilesystemStorage.java:858)
atcom.pega.pegarules.session.internal.mgmt.base.FilesystemStorage.deleteExpiredRequestors(FilesystemStorage.java:794)atcom.pega.pegarules.session.internal.mgmt.base.PassivationCleanerUtils.deleteExpiredRequestors(PassivationCleanerUtils.java:70)
atcom.pegarules.generated.activity.ra_action_cleanupexpired_09716de7c80cb7bb8c4b917089746128.step6_circum0(ra_action_cleanupexpired_09716de7c80cb7bb8c4b917089746128.java:162)
atcom.pegarules.generated.activity.ra_action_cleanupexpired_09716de7c80cb7bb8c4b917089746128.perform(ra_action_cleanupexpired_09716de7c80cb7bb8c4b917089746128.java:70)
...at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:206)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
Caused by: java.io.FileNotFoundException: /path/more_paths/W9CE75743C4DD0A32686292E65423546A/metadata.ser (No such file or directory)at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:158)
atcom.pega.pegarules.storage.fs.direct.FilesystemStorage._getInputStream_privact(FilesystemStorage.java:161)
at com.pega.pegarules.storage.fs.direct.FilesystemStorage.getInputStream(FilesystemStorage.java:136)
at com.pega.pegarules.storage.FileStorageManager.getInputStream(FileStorageManager.java:513)
at com.pega.pegarules.storage.FileStorageUtilsImpl.getInputStream(FileStorageUtilsImpl.java:118)
at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
at java.lang.reflect.Method.invoke(Method.java:620)
at com.pega.pegarules.pub.util.PRInputStream.getInputStream(PRInputStream.java:109)
... 48 more
Steps to Reproduce
Unknown
Root Cause
The errors display as the result of a race condition in which the NodeCleaner agent runs multiple nodes simultaneously. One instance on one node reads files for a passivated requestor that is already removed by another instance of the agent running on another node.There is no loss of data. NodeCleaner that hits the error aborts and proceeds to the next cycle.
Resolution
Apply HFix-41188.
Published October 31, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.