You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2009/10/15 16:00:32 UTC

[jira] Resolved: (WSCOMMONS-506) Temporary copies of MTOM attachments are not deleted from the file system in a timely manner

     [ https://issues.apache.org/jira/browse/WSCOMMONS-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rich Scheuerle resolved WSCOMMONS-506.
--------------------------------------

    Resolution: Fixed

Marking this issue as resolved.

My belief is that additional changes to the management of File resources should be addressed by another JIRA.

> Temporary copies of MTOM attachments are not deleted from the file system in a timely manner
> --------------------------------------------------------------------------------------------
>
>                 Key: WSCOMMONS-506
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-506
>             Project: WS-Commons
>          Issue Type: Bug
>          Components: AXIOM
>            Reporter: Wendy Raschke
>            Assignee: Rich Scheuerle
>         Attachments: WSCOMMONS-506.patch
>
>
> When customers send MTOM attachments having a certain size, the Axis2 runtime uses Axiom to make copies of these attachments and name them with a pattern of AxisXXXXXX.att, where XXXXXX is an arbitrary sequence of integers. These copies may not be deleted in a timely manner, and may be removed only when the JVM exits. This can cause a lot of files to accumulate on the customer's file system and eat up disk space, and some of these files can be quite large.
> Note that the internal sizeThreshold property controls whether attachment files are written to memory or as files to the disk.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.