[
https://issues.apache.org/jira/browse/CXF-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893793#comment-17893793
]
Andriy Redko commented on CXF-9064:
-----------------------------------
Thanks [~exprompt] , that fortunately is true and there are quite a few cases
(both on the server and on the client) where CXF (with caching output stream)
is not able to determine when the tempFile (cache stream) has to be closed. It
is somewhat mitigated by CXF-7396 but the root cause is not fixed.
> AsyncHTTPConduit doesn't close wrappedStream on close
> -----------------------------------------------------
>
> Key: CXF-9064
> URL: https://issues.apache.org/jira/browse/CXF-9064
> Project: CXF
> Issue Type: Bug
> Affects Versions: 3.6.4
> Reporter: Alexey Deryabin
> Priority: Major
>
> I found that in
> org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduit$AsyncWrappedOutputStream
> on close method the wrappedStream is not closed but reassigned to the new
> anonymous OutputStream in handleHeadersTrustCaching by setupWrappedStream.
> It is in cxf-rt-transports-http-hc module.
> My suggest to add out.close() on 426 line.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
