[
https://issues.apache.org/jira/browse/CXF-7396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332077#comment-16332077
]
Grégory edited comment on CXF-7396 at 1/19/18 2:53 PM:
-------------------------------------------------------
I can reproduce this bug by make a call to my SOAP Service and don't wait the
response (for example with JMeter and a HTTP Timeout < response time).
The exception is "caused by com.ctc.wstx.exc.WstxIOException:
java.io.IOException: Broken pipe", but the Temp file isn't properly cleaned.
By this case, in my opinon, the close method of TransferableFileInputStream or
CachedOutputStream is not called. The exception is catched in
JAXBEncoderDecoder.
was (Author: gneuhaus):
I can reproduce this bug by make a call to my SOAP Service and don't wait the
response (for example with JMeter and a HTTP Timeout < response time).
The exception is "caused by com.ctc.wstx.exc.WstxIOException:
java.io.IOException: Broken pipe", but the Temp file isn't properly cleaned.
> CachedOutputStream doesn't delete temp files
> --------------------------------------------
>
> Key: CXF-7396
> URL: https://issues.apache.org/jira/browse/CXF-7396
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.8
> Reporter: Matthew Roth
> Priority: Minor
> Fix For: NeedMoreInfo
>
>
> In the CachedOutputStream the method maybeDeleteTempFile doesn't always
> delete the temp file when it should.
>
> this.streamList.remove(stream)
> Doesn't remove the stream, occasionally the stream is not in the list causing
> the check of this.streamList().isEmpty() to fail. Also occurs when
> this.streamList() contains multiple streams.
> This seems occur when too many large requests are processed in a row.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
