[
https://issues.apache.org/jira/browse/NIFI-13568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868322#comment-17868322
]
ASF subversion and git services commented on NIFI-13568:
--------------------------------------------------------
Commit c31fb9d373907a4f5615c0790c832cf9e87b7218 in nifi's branch
refs/heads/main from Ferenc Kis
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c31fb9d373 ]
NIFI-13568 MiNiFi Fix concurrent SAXParser issue in manifest parsing
Signed-off-by: Ferenc Erdei <[email protected]>
This closes #9098.
> [MiNiFi] Potential SAX parser concurrency issue when sending manifest
> ---------------------------------------------------------------------
>
> Key: NIFI-13568
> URL: https://issues.apache.org/jira/browse/NIFI-13568
> Project: Apache NiFi
> Issue Type: Bug
> Components: MiNiFi
> Affects Versions: 2.0.0-M4
> Reporter: Ferenc Kis
> Assignee: Ferenc Kis
> Priority: Major
> Labels: minifi-java
> Fix For: 2.0.0-M5
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Since NIFI-13123 C2 heartbeats and acknowledgements happen on separate
> threads.
> Heartbeating and the C2 operation UPDATE/CONFIGURATION requires the manifest
> to be loaded and processed, it may occur that the two separate threads will
> try to concurrently load and parse the manifest.
> Since SAXParser is not thread safe, an exception will be thrown, and the
> acknowledge handler thread may stop, and won't be restarted.
> Goals:
> * make the manifest parsing logic thread safe, so concurrent access won't
> result in an error
> * make acknowledge handler logic more robust, so exceptions thrown from
> operation handlers won't cause the thread to exit
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
