[
https://issues.apache.org/jira/browse/CXF-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036722#comment-13036722
]
Freeman Fang commented on CXF-3504:
-----------------------------------
Hi,
Ok, I saw the introduced connection can't release issue, it also only happened
when you not actually read the attachment stream but close it directly.
The fix should be when we close a stream, we needn't check if there's hasNext
attachment(as we intend to close it, we don't care if there's any attachment we
don't read), just mark this stream as closed.
I will append a new patch, could you verify it works for your scenario?
Also, if you wanna contribute your patch you mentioned before, I'm very glad to
review it.
Freeman
> for big attachment, a temporary file is left on disk and keep opend, if the
> application just close the DataSource's inputStream and doesn't consume it;
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-3504
> URL: https://issues.apache.org/jira/browse/CXF-3504
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: ext2
> Assignee: Freeman Fang
> Fix For: 2.4.1, 2.3.5
>
> Attachments: CXF-3504.patch, attachment-clean.zip, mtom.wsdl
>
>
> when the client receiving multiple larget attachments from server. here
> "large" means : attachment size is large enough to be saved as temporary file
> on disk;
> for the last attachment, if the user application only close the input stream
> got from DataSource and doesn't consume the input stream at all, a temporary
> file will be left on the disk.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
