Re: Adding JVM arguments when running NiFi...

2017-01-18 Thread Russell Bateman
Thanks for pointing that out, Mark. The net result of what I wrote is just that: numeric arguments in order of N, then whatever else is there, unsorted. I did nothing, however, to handle conflicting values of N. I don't claim the code I attached to the JIRA to be the best solution, only an ill

Re: Adding JVM arguments when running NiFi...

2017-01-18 Thread Mark Payne
Russ, Sorry - I didn't see this sooner. That is accurate, that 'N' can be non-numeric. By default, in bootstrap.conf, there is actually a property named "java.arg.debug=-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000" but it is commented out. I think that if we want to guara

Re: Adding JVM arguments when running NiFi...

2017-01-18 Thread Russell Bateman
For my own purposes, I fixed this in 0.7.1 /nifi-bootstrap///src/main/java/org/apache/nifi/bootstrap/RunNiFi.java/, but at Joe's suggestion, I created JIRA NIFI-3364 hoping some committer will get to it for all code branches-forward. The solution I used was made to be as little disruptive t

Re: Adding JVM arguments when running NiFi...

2016-12-19 Thread Andrew Grande
Sounds like switching to the LinkedHashMap could address.the JVM startup flags ordering g? Andrew On Thu, Dec 15, 2016, 1:11 PM Russell Bateman wrote: > Joe, > > I have more detail and success to report... > > There is no problem in NiFi /per se/. It was not really necessary to dig > down into

Re: Adding JVM arguments when running NiFi...

2016-12-15 Thread Russell Bateman
Joe, I have more detail and success to report... There is no problem in NiFi /per se/. It was not really necessary to dig down into the code really because there's no problem there. It's just how java.arg./n/is consumed that creates trouble. One must play around with the value of /n/ when arg

Re: Adding JVM arguments when running NiFi...

2016-12-14 Thread Joe Witt
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 wrote: > Of course, as many have done, I've run Java app

Re: Adding JVM arguments when running NiFi...

2016-12-14 Thread Russell Bateman
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 getting love.

Adding JVM arguments when running NiFi...

2016-12-14 Thread Russell Bateman
I've doctored /conf/bootstrap.conf/ to contain these additional lines: java.arg.15=-XX:+UnlockCommercialFeatures java.arg.16=-XX:+FlightRecorder java.arg.17=-XX:StartFlightRecording=duration=120m,filename=recording.jfr In the end, NiFi's grumpy about this and won't start (from /logs/