[
https://issues.apache.org/jira/browse/NIFI-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310884#comment-16310884
]
ASF GitHub Bot commented on NIFI-4726:
--------------------------------------
Github user mgaido91 commented on the issue:
https://github.com/apache/nifi/pull/2363
Thanks for your comment @joewitt. I think we can't fix this in jolt since
the root cause is our concurrent usage of their utilities and fixing it there
seems an overkill to me. What do you think about using a pool instead of the
thread local then?
> 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
>
> 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)
