nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Taft <a...@adamtaft.com>
Subject Re: InvokeHTTP processor loses SSL Context after NiFi restart
Date Thu, 06 Aug 2015 14:13:07 GMT
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 <joe.witt@gmail.com> 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" <john.titus@trustedconcepts.com>
> 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
>>
>

Mime
View raw message