You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Lopata (Jira)" <ji...@apache.org> on 2022/08/09 09:17:00 UTC

[jira] [Updated] (NIFI-10331) Bootstraping NiFI with the java arguments that contains space not possible

     [ https://issues.apache.org/jira/browse/NIFI-10331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lopata updated NIFI-10331:
--------------------------
    Summary: Bootstraping NiFI with the java arguments that contains space not possible  (was: Bootstraping NiFI with the java arguments with space not possible)

> Bootstraping NiFI with the java arguments that contains space not possible
> --------------------------------------------------------------------------
>
>                 Key: NIFI-10331
>                 URL: https://issues.apache.org/jira/browse/NIFI-10331
>             Project: Apache NiFi
>          Issue Type: New Feature
>    Affects Versions: 1.17.0
>         Environment: all
>            Reporter: Lopata
>            Priority: Major
>
> We are running NiFi on Java 17 and we are not able to add _*--add-opens java.base/java.lang.reflect=ALL-UNNAMED*_ java argument when bootstrapping the NiFi. RunNifi.java is using ProcessBuilder that expects command without spaces, so we have to defined --add-opens argument in the bootstrap.conf file with two _*java.arg.N*_ properties. RunNifi.java when creates the java command doesn't respect the order of _*java.arg.N*_ properties and randomly places the --add-opens argument parts into java command which is than not valid.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)