[ 
https://issues.apache.org/jira/browse/NIFI-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502376#comment-16502376
 ] 

Jeff Storck commented on NIFI-5175:
-----------------------------------

[~joewitt]

I created an AWS EC2 instance of REHL 7.5, installed openjdk 10.0.1, and copied 
NiFi built from master (as it was on 6/4/2018) using Java 1.8.0_162.

On the EC2 instance, starting NiFi with openjdk 10.0.1 was successful.

As in the test I ran on docker with the openjdk:10 image, on the RHEL 7.5 AWS 
EC2 instance, the --add-modules=java.xml.bind was added to the command that 
starts NiFi:
{code:java}
2018-06-05 19:18:40,570 INFO [main] org.apache.nifi.bootstrap.Command Command: 
java -classpath 
/home/ec2-user/nifi-1.7.0-SNAPSHOT/./conf:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/javax.servlet-api-3.1.0.jar:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/jetty-schemas-3.1.jar:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/logback-classic-1.2.3.jar:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/logback-core-1.2.3.jar:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/slf4j-api-1.7.25.jar:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/jcl-over-slf4j-1.7.25.jar:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/jul-to-slf4j-1.7.25.jar:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/log4j-over-slf4j-1.7.25.jar:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/nifi-api-1.7.0-SNAPSHOT.jar:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/nifi-framework-api-1.7.0-SNAPSHOT.jar:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/nifi-runtime-1.7.0-SNAPSHOT.jar:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/nifi-nar-utils-1.7.0-SNAPSHOT.jar:/home/ec2-user/nifi-1.7.0-SNAPSHOT/./lib/nifi-properties-1.7.0-SNAPSHOT.jar
 -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m 
-Djavax.security.auth.useSubjectCredsOnly=true 
-Djava.security.egd=file:/dev/urandom 
-Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true 
-Djava.awt.headless=true -Djava.protocol.handler.pkgs=sun.net.www.protocol 
-XX:+UseG1GC 
-Dnifi.properties.file.path=/home/ec2-user/nifi-1.7.0-SNAPSHOT/./conf/nifi.properties
 -Dnifi.bootstrap.listen.port=40142 -Dapp=NiFi 
-Dorg.apache.nifi.bootstrap.config.log.dir=/home/ec2-user/nifi-1.7.0-SNAPSHOT/logs
 --add-modules=java.xml.bind org.apache.nifi.NiFi
{code}

> NiFi built with Java 1.8 needs to run on Java 9
> -----------------------------------------------
>
>                 Key: NIFI-5175
>                 URL: https://issues.apache.org/jira/browse/NIFI-5175
>             Project: Apache NiFi
>          Issue Type: Sub-task
>            Reporter: Jeff Storck
>            Assignee: Jeff Storck
>            Priority: Major
>             Fix For: 1.7.0
>
>
> The following issues have been encountered while attempting to run a Java 
> 1.8-built NiFi on Java 9:
> ||Issue||Solution||Status||
> |JAXB classes cannot be found on the classpath|Add 
> "--add-modules=java.xml.bind" to the commant that starts NiFi|Done|
> |NiFI boostrap not able to determine PID, restarts nifi after nifi.sh 
> stop|Detect if NiFi is running on Java 9, and reflectively invoke 
> Process.pid(), which was newly added to the Process API in Java 9|Done|
>  
> ----
>  
> ||Unaddressed issues/warnings with NiFi compiled on Java 1.8 running on Java 
> 9+||Description||Solution||
> |WARNING: An illegal reflective access operation has occurred
>  ..._specific class usage snipped_...
>  WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
>  WARNING: All illegal access operations will be denied in a future 
> release|Reflective invocations are common in the code used in NiFi and its 
> dependencies in Java 1.8|Full compliant migration to Java 9 and use 
> dependencies that are Java 9 compliant|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to