Chapter 7. Known Issues

If you try to start an embedded server from a management CLI instance that was started using the jboss-cli-client.jar file on JDK 11, you will get an error: WFLYEMB0014: Cannot load module. To avoid this error, you must add --add-modules java.se when starting the management CLI:

java --add-modules java.se -jar jboss-cli-client.jar

$ java --add-modules java.se -jar jboss-cli-client.jar

If a client application directly depends on Artemis client JARs, for example, artemis-jms-client, artemis-commons, artemis-core-client, or artemis-selector, then you must add a dependency in your pom.xml file for wildfly-client-properties:

<dependency>
  <groupId>org.jboss.eap</groupId>
  <artifactId>wildfly-client-properties</artifactId>
</dependency>

<dependency>
  <groupId>org.jboss.eap</groupId>
  <artifactId>wildfly-client-properties</artifactId>
</dependency>

This is to avoid a JMSRuntimeException when calling message.getJMSReplyTo() from an older JBoss EAP 7 client as described in JBEAP-15889.

If you install the JBoss EAP 7.2 RPM packages on RHEL 7 and it only includes the default RHEL JDK 11 package, due to the dependencies currently defined in the packages, the RPM will also install JDK 1.8. This will result in JDK 1.8 being set as the default JDK. For this reason, you must use alternatives to configure the system to use JDK 11.

alternatives --config java

alternatives --config java

Enter the number that corresponds to JDK 11.