Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Write failure during passivation queue processing



Administrators observe repeated errors in the PegaRULES logfile indicating a failure to write passivation data to files on the application server file system.

Error Messages

"Caught exception during passivation processing: /usr/local/oracle/wls-latest/domains/prpc/prpc_deploy/sessions/PassivationData/2/H7FF6D855C065D1B2197397F147BF35B2/metadata.ser (No such file or directory)"

Steps to Reproduce

Not Applicable

Root Cause

A defect or configuration issue in the operating environment. The file system path the Pega engine was writing to did not provide write permission to the user that owns the WebLogic java process. Once write permission was granted the issue was resolved.


Make the following change to the operating environment: Provide write permission to the file system where Pega passivates requestor content.

Suggest Edit

Published March 24, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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