[
https://issues.apache.org/jira/browse/NIFI-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688478#comment-16688478
]
ASF subversion and git services commented on NIFI-5822:
-------------------------------------------------------
Commit 76b0065a67c0e3270d44d85e1933c41bfaba8841 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=76b0065 ]
NIFI-5822: Ensure that we don't call
FlowController.getControllerServiceProvider() before the
ControllerServiceProvider has been initialized
This closes #3171.
Signed-off-by: Bryan Bende <[email protected]>
> ControllerServices not available during @OnScheduled
> ----------------------------------------------------
>
> Key: NIFI-5822
> URL: https://issues.apache.org/jira/browse/NIFI-5822
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.9.0
> Reporter: Peter Wicks
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.9.0
>
>
> If a processor tries to load a ControllerService during `@OnScheduled`, then
> `context.getControllerService` contains a null reference to
> `controllerServiceProvider`. I traced this back to
> `StandardProcessScheduler.startProcessor`, and the reference to
> `controllerServiceProvider` is also `null` here. `ExecuteSQL` acquires it's
> connection during `@OnScheduled`.
> But once we reach `onTrigger`, everything is fine and you can retrieve a
> controller service without issue
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
