cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akitoshi Yoshida (JIRA)" <>
Subject [jira] [Commented] (CXF-6228) Using XSLTFeature with large messages creates unremovable temporary files
Date Mon, 02 Feb 2015 21:54:36 GMT


Akitoshi Yoshida commented on CXF-6228:

The patch has been submitted into master, 3.0.x, and 2.7.x branches. The latest 3.0.4-SNAPSHOT
version should not have this issue. If you could verify it, that would be appreciated.
regards, aki

> Using XSLTFeature with large messages creates unremovable temporary files
> -------------------------------------------------------------------------
>                 Key: CXF-6228
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 3.0.3
>            Reporter: Papp István Péter
>            Assignee: Akitoshi Yoshida
>            Priority: Minor
>         Attachments:
> Using the XSLT transformation feature causes the outgoing message to use a CachedOutputStream
object. If the size of the message is above the configured threshold, a temporary file will
be created to store the message on the disk; however, this file is not deleted after the message
is sent.
> Based on info available on similar problems encountered with CachedOutputStream and attachments,
I tried using an interceptor in the SETUP_ENDING phase to close the stream manually - this,
however, did not work because even after closing the stream, the "streamList" variable was
not empty, which resulted in the closing logic skipping file deletion in the "maybeDeleteTempFile"
method. Attempts to delete the file directly also fail for obvious reasons.
> Some (sometimes all, not sure what makes the difference) of the temporary files are removed
during a clean server shutdown, but since this is a rare event in production environments,
it does not really solve the problem. (Actually, the issue was discovered when the temp files
filled the disk completely on a production server.)
> The only viable workaround I found so far was to set the CachedOutputStream threshold
high enough to avoid caching the data to disk altogether.

This message was sent by Atlassian JIRA

View raw message