Each time a transaction finishes executing, the transaction archive management thread may try to copy all of the files in the transaction's directory to a transaction archive entry (if configured to do so) and then tries to delete the transaction directory. If any file in the transaction directory is open for writing or reading, the transaction archive management thread will be unable to delete the transaction directory and unable to copy the file into the transaction archive. An open, locked file means the management thread will be unable to delete the transaction directory.

The most likely cause of a locked file is an application running in an Arbortext PE sub-process that opens a file and fails to close it. When you develop a custom application, you should check the Arbortext PE Request Manager's log for errors stating that files you open could not be read or deleted as part of testing your application. The management thread will keep trying to copy and delete the files in question at ten second intervals, and the messages in the log will be repeated each time it does so, so the log entries should be apparent.