]
James Perkins commented on WFCORE-3962:
---------------------------------------
I think this is going to be best handled with documentation. For standalone we could
probably just add the module if we know we're using Java 9+. Another option would be
to just have commented out {{JAVA_OPT="--add-modules=java.se $JAVA_OPTS"}} in
the {{standalone.conf}} file.
For domain it would be a manual process anyway. While we could detect Java 9+ for the HC
and DC we can't for the servers.
In the {{domain.conf}} we'd need:
{code}
PROCESS_CONTROLLER_JAVA_OPTS="--add-modules=java.se
$PROCESS_CONTROLLER_JAVA_OPTS"
HOST_CONTROLLER_JAVA_OPTS="--add-modules=java.se $HOST_CONTROLLER_JAVA_OPTS"
{code}
Then the following CLI command would need to be executed:
{code}
/host=master/jvm=default:add-jvm-option(jvm-option="--add-modules=java.se")
{code}
Note though that means the target server is using Java 9+.
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}