[
https://issues.apache.org/jira/browse/NIFI-11232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705678#comment-17705678
]
ASF subversion and git services commented on NIFI-11232:
--------------------------------------------------------
Commit 6bd893da16a3db4a65feb40cb70ed3894d147b5e in nifi's branch
refs/heads/main from Christian Wahl
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6bd893da16 ]
NIFI-11232 Fixed buffer handling in ContentClaimInputStream
This closes #6996
Signed-off-by: David Handermann <[email protected]>
> FlowFileAccessException using ContentClaimInputStream
> -----------------------------------------------------
>
> Key: NIFI-11232
> URL: https://issues.apache.org/jira/browse/NIFI-11232
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.20.0
> Reporter: Christian Wahl
> Priority: Major
> Fix For: 2.0.0, 1.21.0
>
> Attachments: TestContentClaimInputStream.java
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> NIFI-10888 introduced a BufferedInputStream inside of the
> ContentClaimInputStream to speed up rewinding in small flow files (<1MB).
> Under some circumstances it can happen in reset that the delegate stream is
> closed and a new delegate stream is created, but the bufferedIn is not
> recreated with the new delegate.
> During the next read this leads to a situation where it tries to read from
> bufferedIn and bufferedIn in turn tries to read from the old and closed
> delegate stream causing an IOException or FlowFileAccessException.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
