[
https://issues.apache.org/jira/browse/NIFI-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317649#comment-16317649
]
ASF GitHub Bot commented on NIFI-4726:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/2363
Hi @mgaido91 @joewitt , I was investigating the root cause of the issue.
Finally, I think I was able to reproduce the ArrayIndexOutOfBoundsException
with JoltTransformJson processor. You can find details in this Gist with a
reproducible NiFi flow template. NOTE, this is not reproducible anymore with
current NiFi 1.5.0 snapshot, you need to test it with older version of NiFi.
https://gist.github.com/ijokarumawak/65f51ea49029c1eafcc62c39e1a606bc
Does it seem reasonable? If that is the root cause we're looking for, then
it doesn't caused by concurrent use of JsonUtils.
> Concurrency issue with JoltTransformJson
> ----------------------------------------
>
> Key: NIFI-4726
> URL: https://issues.apache.org/jira/browse/NIFI-4726
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Marco Gaido
> Assignee: Marco Gaido
>
> JoltTransformJson uses under the hood Jackson to parse JSONs. On heavy
> multithreading workloads, Jackson can have concurrency problem, as also
> described in this Stackoverflow thread
> https://stackoverflow.com/questions/17924865/jsonmappingexception-was-java-lang-arrayindexoutofboundsexception.
> This can cause all the parsing to fail when this problem occurs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
