[
https://issues.apache.org/jira/browse/NIFI-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505150#comment-16505150
]
ASF GitHub Bot commented on NIFI-5274:
--------------------------------------
Github user mosermw commented on the issue:
https://github.com/apache/nifi/pull/2767
The situation I'm trying to catch uses a regular expression that looks
legitimate, so can't be caught while validating configuration, but then blows
up when the input flowfile causes the Pattern matcher to produce too many
matches while using recursive code. I do think this falls into a Category 3
issue. I simplified the code to catch StackOverflowError and comment why the
catch exists.
> ReplaceText can product StackOverflowError which causes admin yield
> -------------------------------------------------------------------
>
> Key: NIFI-5274
> URL: https://issues.apache.org/jira/browse/NIFI-5274
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.6.0
> Reporter: Michael Moser
> Assignee: Michael Moser
> Priority: Major
>
> Regex Replace mode can easily produce StackOverflowError. Certain regular
> expressions are implemented using recursion, which when used on large input
> text can cause StackOverflowError. This causes the ReplaceText processor to
> rollback and admin yield, which causes the input flowfile to get stuck in the
> input queue.
> We should be able to catch this condition and route the flowfile to failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
