Currently debugging a client application that enabled attachment caching using the following Axis2 properties. org.apache.axis2.Constants.Configuration.CACHE_ATTACHMENTS org.apache.axis2.Constants.Configuration.ATTACHMENT_TEMP_DIR org.apache.axis2.Constants.Configuration.FILE_SIZE_THRESHOLD
>From executing the client application and from stepping through the attachment caching implementation code in Axis2, the attachment is appropriately cached to a specified temp directory in the local file system when the attachment size is greater than the specified attachment size threshold. The apparent problem now is that all cashed attachment (s) for every request/response message are not deleted or reused at the end of every execution hence client application is quickly running out of disk space especially when attachments are fairly large. Any reason(s) for not deleting these cashed attachment after use? Are code already written to delete these attachment(s) from the temp directory after use? If no code exist to clean up the temp directory and I needed to add this support, at what point during the message execution life cycle is it safe to delete these cached attachment from the temp directory? Any thought or suggestion on this will be appreciated.
