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

Archiving and Purging don't stop though there is no permission



Archiving and Purging does not stop though there is no permission on the archiving folder. 

User configured to archive or purge ten items from configuration wizard and when there is no access this seems to be running continuously. User reports that this might lead to server crash. 


Error Messages

2016-01-04 15:24:19,599 [fault (self-tuning)'] [t-Archival] [XYZApp:01.01.01] (rated.pega_procom_archivepurge) ERROR| [email protected] - ExportZipFile: Encountered the following error: /weblogic/103/bea/user_projects/domains/bpm_dev/PegaTemp/Temp/ArchivedWork/ (Permission denied) 
2016-01-04 15:24:19,604 [fault (self-tuning)'] [t-Archival] [XYZApp:01.01.01] (cel_Management_Archival.Action) ERROR| [email protected] - Purging is not attempted as archiving failed. Please check logs for details 

Steps to Reproduce

1. Configure Archive or Purge to process 10 items. 
2. Remove the write access for PRPC batch requestor on ArchivedWork pr_temp folder. 
3. Process the archive action manually.

Root Cause

In case if there is no write privileges for PRPC batch requestor, the Purge & Archive will stop after trying for X number of times.  X depends on number of resolved WorkObjects (WO’s) and the specified items to purge in configuration.

For example, if there are 1400 Resolved-* WO’s and have specified 10 items to purge in configuration – 1400/10 = 140 retries will be there.

This is just a retry mechanism it will not consume memory to exhaust the server.  Therefore, specify the configuration value based on the no of Resolved-* WO’s data.



Here’s the explanation for the reported behavior - 

The number of retries totally depend on the specified configuration or items and number of WorkObjects present in your DB with Resolved status.

When configured properly, this will not cause any server crash.

Ideally the user who is running the PRPC JVM process on Unix server should have the access to PRTemp’s directory which contains Generated java classes, all the static content & passivation data.  

​As the ArchivedWork directory is created inside PRTemp, user should also have write access to the same

Published May 14, 2016 - Updated October 8, 2020

Was this useful?

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.

Did you find this content helpful?

Want to help us improve this content?

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