[
https://issues.jboss.org/browse/WFCORE-4211?page=com.atlassian.jira.plugi...
]
James Perkins commented on WFCORE-4211:
---------------------------------------
The issue is really MODULES-372. I guess this could just be a documentation task. However
you can boot a JVM on Java 11 without the {{--add-module=java.se}} argument and it will
work until it reaches the {{EmbeddedProcessFactory.setupVfsModule()}}. That's the only
argument I have for it being a bug. That's admittedly a bit of a soft argument :)
{code}
Exception in thread "main" java.lang.RuntimeException: WFLYEMB0014: Cannot load
module org.jboss.vfs from: local module loader @75329a49 (finder: local module finder
@161479c6 (roots:
/home/jperkins/servers/wildfly-14.0.1.Final/modules,/home/jperkins/servers/wildfly-14.0.1.Final/modules/system/layers/base))
at
org.wildfly.core.embedded.EmbeddedProcessFactory.setupVfsModule(EmbeddedProcessFactory.java:299)
at
org.wildfly.core.embedded.EmbeddedProcessFactory.createStandaloneServer(EmbeddedProcessFactory.java:154)
at com.jamezp.test.Main.main(Main.java:161)
Caused by: 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.ModuleLoader.loadModule(ModuleLoader.java:280)
at
org.wildfly.core.embedded.EmbeddedProcessFactory.setupVfsModule(EmbeddedProcessFactory.java:297)
... 2 more
{code}
Embedded container does not work without the JVM being launched with
java.se module on Java 11
----------------------------------------------------------------------------------------------
Key: WFCORE-4211
URL:
https://issues.jboss.org/browse/WFCORE-4211
Project: WildFly Core
Issue Type: Bug
Components: Embedded
Reporter: James Perkins
Priority: Major
Labels: Java11
With the embedded API the container can't be started on Java 11 without the
{{--add-module=java.se}} argument being added to the JVM. There may not be a way to solve
this, but it should likely at lest be documented. If this becomes just a documentation
issue then the type should likely be changed to "Task".
--
This message was sent by Atlassian Jira
(v7.12.1#712002)