NiFi supports Java 11 (but default is still 8), newer JDKs are currently not supported.
Cheers, Chris Sampson On Fri, 20 Aug 2021, 13:42 Juan Pablo Gardella, <gardellajuanpa...@gmail.com> wrote: > AFAIK Nifi supports JDK 1.8, other JDK versions probably will not work. > > On Fri, 20 Aug 2021 at 09:24, <mc...@fullvisibility.com> wrote: > >> I've installed NiFi 1.14.0 on a Windows Server 2019 machine with OpenJDK >> 16.0.2. >> No changes to properties or anything, just unzipped these and set the >> PATH and JAVA_HOME environment variables. >> I execute the run-nifi.bat file and it runs for a minute and exits. >> >> The nifi-bootstrap.log file contains this: >> >> >> 2021-08-19 19:29:25,531 INFO [NiFi Bootstrap Command Listener] >> org.apache.nifi.bootstrap.RunNiFi Apache NiFi now running and listening for >> Bootstrap requests on port 62463 >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr java.lang.reflect.InaccessibleObjectException: >> Unable to make protected final java.lang.Class >> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) >> throws java.lang.ClassFormatError accessible: module java.base does not >> "opens java.lang" to unnamed module @6e6ec71f >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at >> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:357) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at >> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at >> java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at >> java.base/java.lang.reflect.Method.setAccessible(Method.java:193) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at >> org.xerial.snappy.SnappyLoader.injectSnappyNativeLoader(SnappyLoader.java:275) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at >> org.xerial.snappy.SnappyLoader.load(SnappyLoader.java:227) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at org.xerial.snappy.Snappy.<clinit>(Snappy.java:48) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at >> org.apache.nifi.processors.hive.PutHiveStreaming.<clinit>(PutHiveStreaming.java:158) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at java.base/java.lang.Class.forName0(Native Method) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at java.base/java.lang.Class.forName(Class.java:466) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at >> org.apache.nifi.nar.StandardExtensionDiscoveringManager.getClass(StandardExtensionDiscoveringManager.java:328) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at >> org.apache.nifi.documentation.DocGenerator.documentConfigurableComponent(DocGenerator.java:100) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at >> org.apache.nifi.documentation.DocGenerator.generate(DocGenerator.java:65) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at >> org.apache.nifi.web.server.JettyServer.start(JettyServer.java:1126) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at org.apache.nifi.NiFi.<init>(NiFi.java:159) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at org.apache.nifi.NiFi.<init>(NiFi.java:71) >> 2021-08-19 19:30:53,137 ERROR [NiFi logging handler] >> org.apache.nifi.StdErr at org.apache.nifi.NiFi.main(NiFi.java:303) >> 2021-08-19 19:30:53,215 INFO [main] org.apache.nifi.bootstrap.RunNiFi >> NiFi never started. Will not restart NiFi >> >> >> >> Maybe this is an OpenJDK issue? >> >> TBH, I haven't spent nearly enough time reading the docs at this point >> but I thought it might just run out of the box. So, it could be operator >> error on my part too. >> >> Thoughts? >> >> Thanks, >> >> Matt >> >
