[
https://issues.apache.org/jira/browse/NIFI-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886457#comment-15886457
]
Russell Bateman commented on NIFI-3364:
---------------------------------------
Sorry, I don't know why the attachment didn't take. I'm struggling to figure
out how to do it. I'll keep trying.
> NiFi start-up fails to honor N in definitions java.arg.N as made in
> conf/bootstrap.conf
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-3364
> URL: https://issues.apache.org/jira/browse/NIFI-3364
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 0.8.0, 0.7.1, 1.2.0, 1.1.1, 1.0.1
> Environment: Any and all platforms and environments.
> Reporter: Russell Bateman
> Priority: Critical
> Labels: easyfix, patch
>
> In albeit rare cases, JVM argument ordering is important. The present
> implementation of the sense of java.arg.N leaves N ignored in the final list
> when presented to the JVM at launch.
> Two examples of insurmountably critical ordering are the use the Java Flight
> Recorder and the JMX remote arguments in support of using Java Mission
> Control remotely to connect to and profile (what's being done by) NiFi.
> Attached is a coded solution for replacing this block of code in RunNiFi.java:
> for (final Map.Entry<String, String> entry : props.entrySet()) {
> final String key = entry.getKey();
> final String value = entry.getValue();
>
> if (key.startsWith("java.arg")) {
> javaAdditionalArgs.add(value);
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
