[jboss-jira] [JBoss JIRA] (WFCORE-3962) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619630#comment-13619630 ] 

James Perkins commented on WFCORE-3962:
---------------------------------------

[~brian.stansberry] Can't different JVM's be defined for servers? So the HC could be running on Java 8 while a server is running on Java 11. We'd have to execute a new process and gather server information from it some how when we generate the launch commands.

> Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se
> -------------------------------------------------------------------------------
>
>                 Key: WFCORE-3962
>                 URL: https://issues.jboss.org/browse/WFCORE-3962
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Management, Modules, Scripts
>    Affects Versions: 6.0.0.Alpha3
>            Reporter: Matej Novotny
>            Assignee: Richard Opalka
>            Priority: Blocker
>              Labels: Java11, blocker-WF14
>
> As per request, copying MODULES-372 to WFCORE as well.
> Starting WFLY with JDK 11 using {{standalone.sh}} yields:
> {code}
> org.jboss.modules.ModuleNotFoundException: java.se
> 	at org.jboss.modules.Module.addPaths(Module.java:1266)
> 	at org.jboss.modules.Module.link(Module.java:1622)
> 	at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> 	at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> 	at org.jboss.modules.Main.main(Main.java:437)
> {code}
> Output of {{java -version}}:
> {code}
> openjdk version "11-ea" 2018-09-25
> OpenJDK Runtime Environment 18.9 (build 11-ea+21)
> OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode)
> {code}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)