[
https://issues.apache.org/jira/browse/NIFI-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wietze B updated NIFI-5434:
---------------------------
Description:
I have a number of ExecuteScript processors running Jython that import
libraries such as {{threading}}, {{urllib3}}, {{requests}}, etc.
When I boot up my machine or initially start the NiFi service, the
ExecuteScript processors relying on external libraries usually to don't work
straight away, throwing {{AttributeError}} s or {{ImportError}} s on libraries
that definitely exist and are accessible. Restarting the machine or the NiFi
service again usually fixes the problem, but it is unclear to me why the
imports sometimes fail, and sometimes work.
See attached two screenshots and an extract from the logs.
was:
I have a number of ExecuteScript processors running Jython that import
libraries such as {{threading}}, {{urllib3}}, {{requests}}, etc.
When I boot up my machine or initially start the NiFi service, the
ExecuteScript processors relying on external libraries usually to don't work
straight away, throwing {{AttributeError}} s or {{ImportError}} s on libraries
that definitely exist and are accessible. Restarting the machine or the NiFi
service again usually fixes the problem, but it is unclear to me why the
imports sometime fail, and sometimes work.
See attached two screenshots and an extract from the logs.
> ExecuteScript/Jython imports fail randomly
> ------------------------------------------
>
> Key: NIFI-5434
> URL: https://issues.apache.org/jira/browse/NIFI-5434
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.6.0, 1.7.0, 1.7.1
> Environment: Debian Stretch (9.5)
> Reporter: Wietze B
> Priority: Major
> Attachments: ibm.png, java_thread.png, log_extract.log
>
>
> I have a number of ExecuteScript processors running Jython that import
> libraries such as {{threading}}, {{urllib3}}, {{requests}}, etc.
> When I boot up my machine or initially start the NiFi service, the
> ExecuteScript processors relying on external libraries usually to don't work
> straight away, throwing {{AttributeError}} s or {{ImportError}} s on
> libraries that definitely exist and are accessible. Restarting the machine or
> the NiFi service again usually fixes the problem, but it is unclear to me why
> the imports sometimes fail, and sometimes work.
> See attached two screenshots and an extract from the logs.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
