Noticing that the \CA\PAM\server\c2o\tmp\ directory is filling with files.
What are these files and can be deleted?
Files in CA\PAM\server\c2o\tmp folder are temporary files used during the execution of Process instances. An instance will create a temp file when necessary and clean it up after completion. It also utilizes this folder if there is a chance there is not enough Memory available to Java.
If you would like to clear that directory you can stop the Orchestrator, then clear that folder out.
If a Process needs something that it does not find in the temp dir it will recreate it.
The best way to help ensure that that folder stays trim is to ensure that within the \pam\server\c2o\bin\C2osvcw.conf file, that you have enough memory configured, and that both the init and the max memory are the same.
Review the java.exe process in Task manager, make note of the average memory usage.
Then modify the \pam\server\c2o\bin\C2osvcw.conf file memory settings to a higher value. For example if the Java.exe process averages 3.4gb of memory usage set PAM to use 4gb and ensure that both init and max memory match:
# Initial Java Heap Size (in MB)
# Maximum Java Heap Size (in MB)
This will take effect the next time the Orchestrator is restarted. May this change to all nodes in a cluster.
If you are using Process Automation 4.1 there were issues with this automatic cleanup action. Matching the memory settings will help keep the tmp folder trim, and once you have updated to the latest release, 4.2 sp2, or 4.3, there should not be an issue with files building up in the tmp directory.
\CA\PAM\server\c2o\tmp\ directory was commonly used for older versions of PAM 4.1 - 4.2
Later releases, from PAM 4.3 onwards, will write such materials to the location identified by the TEMP environment variable, which may vary per installation, such as C:\Users\Appdata\Local\Temp\.c2otmp or C:\Temp\.c2otmp
For PAM 4.4 or any release that uses the wildfly backend infrastructure, the location will be C:\Program Files\CA\PAM\wildfly\standalone\tmp