Mailing-List: contact dev-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
MIME-Version: 1.0
In-Reply-To: <e97759b8-1797-6680-9798-02a1cc6bbdad@windofkeltia.com>
References: <585189F5.2090102@windofkeltia.com> <e97759b8-1797-6680-9798-02a1cc6bbdad@windofkeltia.com>
From: Joe Witt <joe.witt@gmail.com>
Date: Wed, 14 Dec 2016 21:41:28 -0500
Message-ID: <CALJK9a5Naa33av3miYy=sqM8SURug9Pz-PH8dDQO_zfmS5Td-Q@mail.gmail.com>
Subject: Re: Adding JVM arguments when running NiFi...
To: dev@nifi.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 15 Dec 2016 02:41:44 -0000

The way you set it up initially is what I'd thought would have done
the trick.  Perhaps we're not ordering the arguments in the same
manner supplied.  Will need to look into that.

Thanks
Joe

On Wed, Dec 14, 2016 at 9:00 PM, Russell Bateman <russ@windofkeltia.com> wr=
ote:
> Of course, as many have done, I've run Java applications with JFR enabled
> using these options against this very JVM (jdk1.8.0_112). So, it isn't a
> problem for the JVM I'm using. I haven't finished digging down into
> ProcessBuilder, or deeper, to figure out why these options are not gettin=
g
> love. I'll get back at it tomorrow and report back.
>
>
> On 12/14/2016 11:05 AM, Russell Bateman wrote:
>>
>>
>> I've doctored /conf/bootstrap.conf/ to contain these additional lines:
>>
>>     java.arg.15=3D-XX:+UnlockCommercialFeatures
>>     java.arg.16=3D-XX:+FlightRecorder
>>
>> java.arg.17=3D-XX:StartFlightRecording=3Dduration=3D120m,filename=3Dreco=
rding.jfr
>>
>>
>> In the end, NiFi's grumpy about this and won't start (from
>> /logs/nifi-bootstrap.log/):
>>
>> 2016-12-14 10:39:36,489 ERROR [NiFi logging handler]
>> org.apache.nifi.StdErr Error: *To use 'FlightRecorder', first unlock usi=
ng
>> -XX:+UnlockCommercialFeatures.*
>> 2016-12-14 10:39:36,489 ERROR [NiFi logging handler]
>> org.apache.nifi.StdErr Error: Could not create the Java Virtual Machine.
>> 2016-12-14 10:39:36,489 ERROR [NiFi logging handler]
>> org.apache.nifi.StdErr Error: A fatal exception has occurred. Program wi=
ll
>> exit.
>> 2016-12-14 10:39:36,507 INFO [main] org.apache.nifi.bootstrap.RunNiFi Ni=
Fi
>> never started. Will not restart NiFi
>>
>> I tried using all options as one (in case the order is disturbed, which =
it
>> was):
>>
>>
>> java.arg.15=3D-XX:+UnlockCommercialFeatures-XX:+FlightRecorder-XX:StartF=
lightRecording=3Dduration=3D120m,filename=3Drecording.jfr
>>
>>
>> and then I get:
>>
>> *2016-12-14 10:50:07,574 ERROR [NiFi logging handler]
>> org.apache.nifi.StdErr Unrecognized VM option 'UnlockCommercialFeatures
>> -XX:+FlightRecorder
>> -XX:StartFlightRecording=3Dduration=3D120m,filename=3Drecording.jfr'*
>> 2016-12-14 10:50:07,574 ERROR [NiFi logging handler]
>> org.apache.nifi.StdErr Error: Could not create the Java Virtual Machine.
>> 2016-12-14 10:50:07,574 ERROR [NiFi logging handler]
>> org.apache.nifi.StdErr Error: A fatal exception has occurred. Program wi=
ll
>> exit.
>> 2016-12-14 10:50:07,598 INFO [main] org.apache.nifi.bootstrap.RunNiFi Ni=
Fi
>> never started. Will not restart NiFi
>>
>> Here's the second command line from /logs/nifi-bootstrap.log/, which I'v=
e
>> wrapped for convenience in reading (see JVM version here too):
>>
>> 2016-12-14 10:56:40,526 INFO [main] org.apache.nifi.bootstrap.Command
>> Working Directory: /home/russ/dev/nifi/nifi-1.1.0
>> 2016-12-14 10:56:40,526 INFO [main] org.apache.nifi.bootstrap.Command
>> Command: */home/russ/dev/jdk1.8.0_112/bin/java*
>> -classpath
>> /home/russ/dev/nifi/nifi-1.1.0/./conf:/home/russ/dev/nifi/nifi-1.1.0/./l=
ib/jcl-over-slf4j-1.7.12.jar:/home/russ/dev/nifi/nifi-1.1.0/./lib/logback-c=
ore-1.1.3.jar:/home/russ/dev/nifi/nifi-1.1.0/./lib/nifi-documentation-1.1.0=
.jar:/home/russ/dev/nifi/nifi-1.1.0/./lib/nifi-nar-utils-1.1.0.jar:/home/ru=
ss/dev/nifi/nifi-1.1.0/./lib/logback-classic-1.1.3.jar:/home/russ/dev/nifi/=
nifi-1.1.0/./lib/jul-to-slf4j-1.7.12.jar:/home/russ/dev/nifi/nifi-1.1.0/./l=
ib/nifi-runtime-1.1.0.jar:/home/russ/dev/nifi/nifi-1.1.0/./lib/slf4j-api-1.=
7.12.jar:/home/russ/dev/nifi/nifi-1.1.0/./lib/nifi-api-1.1.0.jar:/home/russ=
/dev/nifi/nifi-1.1.0/./lib/nifi-framework-api-1.1.0.jar:/home/russ/dev/nifi=
/nifi-1.1.0/./lib/log4j-over-slf4j-1.7.12.jar:/home/russ/dev/nifi/nifi-1.1.=
0/./lib/nifi-properties-1.1.0.jar
>> -Dorg.apache.jasper.compiler.disablejsr199=3Dtrue
>> -Xmx512m
>> -Xms512m
>> -agentlib:jdwp=3Dtransport=3Ddt_socket,server=3Dy,suspend=3Dn,address=3D=
9191
>> *-XX:+UnlockCommercialFeatures
>> -XX:+FlightRecorder
>> -XX:StartFlightRecording=3Dduration=3D120m,filename=3Drecording.jfr*
>> -Dsun.net.http.allowRestrictedHeaders=3Dtrue
>> -Djava.net.preferIPv4Stack=3Dtrue
>> -Djava.awt.headless=3Dtrue
>> -XX:+UseG1GC
>> -Djava.protocol.handler.pkgs=3Dsun.net.www.protocol
>>
>> -Dnifi.properties.file.path=3D/home/russ/dev/nifi/nifi-1.1.0/./conf/nifi=
.properties
>> -Dnifi.bootstrap.listen.port=3D41736
>> -Dapp=3DNiFi
>>
>> -Dorg.apache.nifi.bootstrap.config.log.dir=3D/home/russ/dev/nifi/nifi-1.=
1.0/logs
>> org.apache.nifi.NiFi
>>
>> Last, I frantically tried this:
>>
>>     java.arg.15=3D"-XX:+UnlockCommercialFeatures -XX:+FlightRecorder
>>     -XX:StartFlightRecording=3Dduration=3D120m,filename=3Drecording.jfr"
>>
>>
>> and then got:
>>
>> *2016-12-14 11:01:36,659 ERROR [NiFi logging handler]
>> org.apache.nifi.StdErr Error: Could not find or load main class
>> "-XX:+UnlockCommercialFeatures -XX:+FlightRecorder
>> -XX:StartFlightRecording=3Dduration=3D120m,filename=3Drecording.jfr"*
>>
>>
>> What's the canonical way of adding/inserting my own JVM commands?
>> Alternatively, is NiFi analyzing and blocking -XX:arguments to the JVM a=
s
>> illegal or unrecognized?
>>
>> Thanks,
>>
>> Russ
>
>