org.jboss.modules.ModuleNotFoundException: java.se

[mayerw01]

When running appclient.sh in Java HotSpot version "11.0.1" I get an exeception

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)

I've found a solution for openjdk version "11-ea" [MODULES-372] JDK 11 - module not found java.se - JBoss Issue Tracker

But this does not work in Java HotSpot.

Does anybody have a solution for Java HotSpot?

[simkam]

Hi,

I think it is [WFLY-10937] Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se - JBoss Issue Tracker  which will be fixed in WildFly 15.

[mayerw01]

This link refers to the same issue. But I've now made the change the appclient.sh

eval \"$JAVA\" $JAVA_OPTS \

--add-modules java.se \

-cp "$CLASSPATH" \

...

This seems to work

[jenskreidler]

Thanks Wolfgang for your workaround, nevertheless I had the following issues:

- adding jvm arguments in arquillian.xml will not work when using a remote-container, and as far as I know the "wildfly-arquillian-container-embedded" is entitled embedded but will bootstrap a fully-fledged server - not any embedded wildfly libraries (so behaves like expected in my case as "remote container")

- using wildfly-arquillian-container-embedded in verion 2.2.0.Final still needs the jvm argument "--add-modules=java.se"

- In my case I added the configuraion in the maven-failsafe configuration:

<configuration>     
<argLine>--add-modules=java.se</argLine>
[...]
</configuration>