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

Brian Stansberry (JIRA) issues at jboss.org
Wed Aug 15 16:44:00 EDT 2018


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

Brian Stansberry commented on WFCORE-3962:
------------------------------------------

[~jamezp] Right. One way or the other that's what we'd have to do in scripts as well. Or something imaginative that's probably just as complex.

I'm not saying this is trivial. And domain servers add another scenario to the problem and thus add to scope. But it doesn't multiply scope or add some fundamentally different problem. 

> 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)


More information about the jboss-jira mailing list