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 "Wendy Raschke (JIRA)" <ji...@apache.org> on 2009/10/02 19:21:23 UTC
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12761649#action_12761649 ]
Wendy Raschke commented on WSCOMMONS-506:
-----------------------------------------
Note that I have a tentative code solution for this, so there is no need for anyone to work on this right now.
> 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
>
> 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.