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!
---