[
https://issues.apache.org/jira/browse/NIFI-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309949#comment-16309949
]
ASF GitHub Bot commented on NIFI-4726:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2363
We should avoid the use of ThreadLocal storage completely. NiFi will not
give the same thread back to the same processor with any guarantees at all. So
we'd be caching/caching/caching and perhaps even leaking information across
threads like that. I think we should work the root cause angle with jolt
> 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)
