Troubleshooting the removal of files that are no longer needed

This directory is the general-purpose temporary directory for assorted processes. It can be cleared once there are no JVMs running in that profile.

This directory is used primarily for file transfers when you are updated applications or configuration information. Empty subdirectories can remain after transfers are completed. These subdirectories can be cleared once there are no JVMs running in that profile.

This directory is used primarily to contain subfolders that represent a workspace session. When functions that access configuration data is invoked from the console or scripting, a workspace session is created and the relevant configuration files are copied into that directory. Should the file or files be updated, the session facilitates atomic updates and conflict management across multiple sessions.

Sessions are cleaned up one ConfigService save() or discard() is called on the session, or once workspace.remove() is called. If neither is done, they can persist and consume disk space, and in some cases memory can be consumed.

Sessions persist across server restarts. If a user that has made configuration updates accidentally or intentionally gets logged out before you save or discard, the session can be recovered on a subsequent login and the work can be resumed.

Cleaning up these folders when no JVMs are running is safe, however you will lose the pending updates from any interrupted sessions.

If a script or other code call functions that access or manipulate configuration files, but then not call, save, or discard upon completion, a workspace directory remains. Such an instance can cause the wstemp directory to grow rapidly if it is being run frequently.