[
https://issues.apache.org/jira/browse/NIFI-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311369#comment-16311369
]
ASF GitHub Bot commented on NIFI-4726:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2363
@mgaido91 If the root problem appears to be that the jolt object needed is
not thread safe then using a pool of lazily initialized objects makes great
sense. You can create them when one is not available and return it to the pool
and that will naturally max out at total num threads for that processor. You
can clear out the pool whenever the processor is unscheduled.
Thanks!
> 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)
