From issues-return-96665-archive-asf-public=cust-asf.ponee.io@nifi.apache.org  Fri May  1 14:48:02 2020
Return-Path: <issues-return-96665-archive-asf-public=cust-asf.ponee.io@nifi.apache.org>
X-Original-To: archive-asf-public@cust-asf.ponee.io
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [207.244.88.153])
	by mx-eu-01.ponee.io (Postfix) with SMTP id 1EB2C180634
	for <archive-asf-public@cust-asf.ponee.io>; Fri,  1 May 2020 16:48:02 +0200 (CEST)
Received: (qmail 65826 invoked by uid 500); 1 May 2020 14:48:01 -0000
Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@nifi.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@nifi.apache.org>
List-Post: <mailto:issues@nifi.apache.org>
List-Id: <issues.nifi.apache.org>
Reply-To: dev@nifi.apache.org
Delivered-To: mailing list issues@nifi.apache.org
Received: (qmail 65813 invoked by uid 99); 1 May 2020 14:48:01 -0000
Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 May 2020 14:48:01 +0000
Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172])
	by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A15C0E2EE5
	for <issues@nifi.apache.org>; Fri,  1 May 2020 14:48:00 +0000 (UTC)
Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1])
	by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 1282678007F
	for <issues@nifi.apache.org>; Fri,  1 May 2020 14:48:00 +0000 (UTC)
Date: Fri, 1 May 2020 14:48:00 +0000 (UTC)
From: "ASF subversion and git services (Jira)" <jira@apache.org>
To: issues@nifi.apache.org
Message-ID: <JIRA.13301567.1588080705000.80019.1588344480075@Atlassian.JIRA>
In-Reply-To: <JIRA.13301567.1588080705000@Atlassian.JIRA>
References: <JIRA.13301567.1588080705000@Atlassian.JIRA> <JIRA.13301567.1588080705764@jira-he-de>
Subject: [jira] [Commented] (NIFI-7404) Scripted processors become invalid
 when thread terminated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/NIFI-7404?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D17097=
406#comment-17097406 ]=20

ASF subversion and git services commented on NIFI-7404:
-------------------------------------------------------

Commit aa986e0bfb6b787fd16de82e4708def42ea0f6af in nifi's branch refs/heads=
/master from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=3Dnifi.git;h=3Daa986e0 ]

NIFI-7404: Fixed invalid script processors upon thread termination

Signed-off-by: Pierre Villard <pierre.villard.fr@gmail.com>

This closes #4238.


> Scripted processors become invalid when thread terminated
> ---------------------------------------------------------
>
>                 Key: NIFI-7404
>                 URL: https://issues.apache.org/jira/browse/NIFI-7404
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> As reported on the NiFi users mailing list, when a processor thread is te=
rminated for ExecuteScript or InvokeScriptedProcessor, the processor become=
s invalid with the message "=E2=80=98Script engine=E2=80=99 validated again=
st =E2=80=98<script engine name>=E2=80=99 is invalid because Given value no=
t found in allowed set =E2=80=98ECMA Script=E2=80=99".
> This is caused by the scriptingComponentHelper not being re-initialized c=
orrectly. When createResources() is called, it is called from a thread whos=
e context classloader is not the processor's instance classloader, and thus=
 none of the additional script engines are found.
> This could be fixed by NIFI-6386, but specifically for these processors t=
here is another solution, namely to add an OnAdded method that calls create=
Resources() whether some other thread has already called it. The OnAdded me=
thod is guaranteed to be called with the thread's context class loader set =
to the processor's instance classloader, and will set the initialized flag =
to true, preventing any future calls (of other methods) of createResources(=
) if not initialized.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)