Sounds like a pretty safe plan. You said your development instance is at 1.1 and your prod on 1.3. Is that right? If it is, you might want to shutdown, backup NiFi and just do a clean installation without bringing over your security settings until you have NiFi 1.6 up and running because a lot has changed between 1.1 and 1.6 from what I understand.
On Wed, May 30, 2018 at 8:57 AM Saip, Alexander (NIH/CC/BTRIS) [C] < [email protected]> wrote: > Hi Mike, > > > > Thanks for the warning. In prod, we are still running NiFi 1.3 with Java > 8. I guess for now, I will just install the JRE 8 onto the dev server, and > experiment with NiFi 1.7 at a later stage. > > > > *From:* Mike Thomsen <[email protected]> > *Sent:* Wednesday, May 30, 2018 8:49 AM > > > *To:* [email protected] > *Subject:* Re: NiFi 1.6.0 fails to start > > > > Alexander, > > > > You're welcome to try the patch in a dev environment and send us feedback > on what you find. The more the merrier in that respect, however, just to be > clear... this is absolutely not recommended as an immediate production fix > for your issue (assuming this environment you're emailing about is a > production one). If it is a prod environment, you have to go the Java 8 > route for now to resolve this for your client. > > > > Thanks, > > > > Mike > > > > On Wed, May 30, 2018 at 8:14 AM Saip, Alexander (NIH/CC/BTRIS) [C] < > [email protected]> wrote: > > Excellent, thanks everyone! Let me try the patch first. Plan B would be to > install Java 8 and bootstrap NiFi to it. > > > > *From:* Mike Thomsen <[email protected]> > *Sent:* Wednesday, May 30, 2018 7:59 AM > *To:* [email protected] > *Subject:* Re: NiFi 1.6.0 fails to start > > > > We added a patch for 1.7.0-SNAPSHOT that should handle that issue going > forward. You're welcome to download the code and try a build (in your dev > environment obviously) to see if that solves your problem. > > > > On Wed, May 30, 2018 at 7:43 AM Bryan Bende <[email protected]> wrote: > > Hello, > > > > There is some work being done to support Java 9/10, but at this time NiFi > currently requires Java 8. > > > > There is an issue when using Java 9/10 where some javax.xml classes are > now part of the JDK, but before NiFi had to bundle them, so it creates > conflicting classes. > > > > Thanks, > > > > Bryan > > > > On May 30, 2018, at 7:20 AM, Saip, Alexander (NIH/CC/BTRIS) [C] < > [email protected]> wrote: > > > > Hello, > > > > We have recently tried to upgrade the development instance of NiFi running > on Windows 2012 from 1.1.1 to 1.6.0, following the process described here > <https://cwiki.apache.org/confluence/display/NIFI/1.x.0+to+1.x.0+Upgrade>. > Both versions are very much vanilla in terms of configuration (no > authentications), but v.1.6.0 fails to start – the content of the > nifi-app.log file follows: > > > > 2018-05-25 14:57:14,032 INFO [main] org.eclipse.jetty.util.log Logging > initialized @17556ms to org.eclipse.jetty.util.log.Slf4jLog > > 2018-05-25 14:57:14,404 ERROR [main] org.apache.nifi.NiFi Failure to > launch NiFi due to java.util.ServiceConfigurationError: > org.apache.nifi.authorization.UserGroupProvider: > org.apache.nifi.authorization.FileUserGroupProvider Unable to get public > no-arg constructor > > java.util.ServiceConfigurationError: > org.apache.nifi.authorization.UserGroupProvider: > org.apache.nifi.authorization.FileUserGroupProvider Unable to get public > no-arg constructor > > at java.base/java.util.ServiceLoader.fail(Unknown Source) > > at java.base/java.util.ServiceLoader.getConstructor(Unknown Source) > > at java.base/java.util.ServiceLoader.access$1000(Unknown Source) > > at > java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(Unknown > Source) > > at > java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(Unknown > Source) > > at java.base/java.util.ServiceLoader$2.hasNext(Unknown Source) > > at java.base/java.util.ServiceLoader$3.hasNext(Unknown Source) > > at > org.apache.nifi.nar.ExtensionManager.loadExtensions(ExtensionManager.java:148) > > at > org.apache.nifi.nar.ExtensionManager.discoverExtensions(ExtensionManager.java:123) > > at > org.apache.nifi.web.server.JettyServer.start(JettyServer.java:771) > > at org.apache.nifi.NiFi.<init>(NiFi.java:157) > > at org.apache.nifi.NiFi.<init>(NiFi.java:71) > > at org.apache.nifi.NiFi.main(NiFi.java:292) > > Caused by: java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException > > at java.base/java.lang.Class.getDeclaredConstructors0(Native Method) > > at java.base/java.lang.Class.privateGetDeclaredConstructors(Unknown > Source) > > at java.base/java.lang.Class.getConstructor0(Unknown Source) > > at java.base/java.lang.Class.getConstructor(Unknown Source) > > at java.base/java.util.ServiceLoader$1.run(Unknown Source) > > at java.base/java.util.ServiceLoader$1.run(Unknown Source) > > at java.base/java.security.AccessController.doPrivileged(Native > Method) > > ... 12 common frames omitted > > Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException > > at java.base/java.net.URLClassLoader.findClass(Unknown Source) > > at java.base/java.lang.ClassLoader.loadClass(Unknown Source) > > at java.base/java.lang.ClassLoader.loadClass(Unknown Source) > > ... 19 common frames omitted > > > > As for the JVM on that server, here is its version: > > > > >java -version > > java version "10.0.1" 2018-04-17 > > Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10) > > Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode) > > > > I have searched this mailing list archive and Google for a clue, but was > unsuccessful so far. > > > > Thanks in advance, > > > > Alexander > > > >
