[
https://issues.apache.org/jira/browse/MINIFICPP-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gábor Gyimesi updated MINIFICPP-2771:
-------------------------------------
Status: Patch Available (was: In Progress)
> Concurrent triggers of processors crash using state manager
> -----------------------------------------------------------
>
> Key: MINIFICPP-2771
> URL: https://issues.apache.org/jira/browse/MINIFICPP-2771
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
> Reporter: Gábor Gyimesi
> Assignee: Gábor Gyimesi
> Priority: Critical
> Fix For: 1.0.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> With the change of creating separate context for each thread of a processor
> in https://issues.apache.org/jira/browse/MINIFICPP-2693 we introduced a bug
> using the state manager. The usual practice is to create a state manager in
> the onSchedule method and store that for later use in onTrigger. With the
> introduction of creating separate ProcessContexts for scheduling and each
> trigger thread the state manager created in onSchedule is not available in
> onTrigger, it is just a dangling pointer which causes the crash.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
