[
https://issues.apache.org/jira/browse/CXF-9064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886936#comment-17886936
]
Alexey Deryabin edited comment on CXF-9064 at 10/29/24 11:22 AM:
-----------------------------------------------------------------
Thank you [~reta] for quick response.
You are right, the {{wrappedStream}} is closed by the {{super.close()}} call
chain but my concern is about the local variable {{out}} which is pointed to
the old {{wrappedStream}}.
You never close old stream that is why tempFile is leaking in some cases.
was (Author: JIRAUSER287381):
Thank you [~reta] for quick response.
You are right, the {{wrappedStream}} is closed by the {{super.close()}} call
chain but my concern about the local variable {{out}} which is pointed to the
old {{wrappedStream}}.
You never close old stream that is why tempFile is leaking in some cases.
> 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)
