This might be related to the "old" way of finding the SSLContext from the controller service. I believe InvokeHTTP doesn't use the updated asControllerService() style. Might be where this is breaking down. Definitely a stack trace would help.
Adam On Thu, Aug 6, 2015 at 10:01 AM, Joe Witt <[email protected]> wrote: > I would say not a known issue. Can you possibly provide the stack > trace/logs? > > That sounds super annoying though. We def want to fix. > > Thanks > Joe > On Aug 6, 2015 9:51 AM, "John Titus" <[email protected]> > wrote: > >> Several of our flows use InvokeHTTP with a "SSL Context Service". If we >> need to restart NiFi, those processors start throwing errors. To fix it, >> we have to modify the config to have no SSL context, Apply the changes, >> then modify the config back to the correct SSL context. >> >> Is this a known issue, or do we perhaps some config wrong somewhere? >> >> John >> >
