[
https://issues.apache.org/jira/browse/WSCOMMONS-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765549#action_12765549
]
Rich Scheuerle commented on WSCOMMONS-506:
------------------------------------------
Andreas,
Okay, I understand your concern, and I will follow-up with more comments later
today.
I agree that the current solution is a necessary fallback when Axis2/Axiom or
customer code fails to properly manage the lifecycle of the resource.
I agree that this fallback is a tactical solution. More work may be necessary
in Axiom attachments to (a) understand and (b) correctly manage the lifecycle
of file resources.
Thanks for digging.
> 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.
