java.net.HttpClient not found in Wildfly 17 and JDK 11

[andre.kornetzky]

When I deploy my war module, I get the following error:

14:37:30,565 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."webservice-impl-1-3.0.0.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."webservice-impl-1-3.0.0.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "webservice-impl-1-3.0.0.war"

at [e-mail]//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)

at [e-mail]//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1737)

at [e-mail]//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1699)

at [e-mail]//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1557)

at [e-mail]//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)

at [e-mail]//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)

at [e-mail]//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)

at [e-mail]//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)

at java.base/java.lang.Thread.run(Thread.java:835)

Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class XXX with ClassLoader ModuleClassLoader for Module "deployment.webservice-impl-1-3.0.0.war" from Service Module Loader

at [e-mail]//org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:78)

at [e-mail]//org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:57)

at [e-mail]//org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.handleAnnotations(InterceptorAnnotationProcessor.java:106)

at [e-mail]//org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:91)

at [e-mail]//org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:76)

at [e-mail]//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)

... 8 more

Caused by: java.lang.NoClassDefFoundError: Ljava/net/http/HttpClient;

at java.base/java.lang.Class.getDeclaredFields0(Native Method)

at java.base/java.lang.Class.privateGetDeclaredFields(Class.java:3067)

at java.base/java.lang.Class.getDeclaredFields(Class.java:2254)

at [e-mail]//org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:72)

at [e-mail]//org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:70)

... 13 more

Caused by: java.lang.ClassNotFoundException: java.net.http.HttpClient from [Module "deployment.webservice-impl-1-3.0.0.war" from Service Module Loader]

at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)

at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)

at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)

at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)

... 18 more

I am using a Windows 10 environment with JDK 11 installed. I start the Wildfly Server version 17.0.1 in Eclipse 2019-06 with the JBoss Tools 4.12.0.Final. In the settings under "Runtime Environment", the Java 11 version is entered correctly.

In the same environment is also a Wildfly 16.0.0 installed. There the war module starts without errors.

Is there a bug in the current Wildfly version?

[ctomc]

looks like that default shipped jboss modules configuration was not yet updated to add the new packages for java.net.http.

probably easiest fix (not necessary the best one) would be to open WILDFLY_HOME/modules/system/layers/base/sun/jdk/main/module.xml

and add line

<path name="java/net/http"/>

and restart the server.

it would also be wise to create new jira issue in http://issues.jboss.org/browse/WFLY so that proper fix for this can be tracked.

[jaikiran]

Previously, before WildFly 17.x, the "java.se" module was added to the runtime when the server was started using a Java version that supported Java modules (Java 9+ runtimes). However, it looks like this was changed in WildFly 17.x as part of this upgrade [WFCORE-4415] Upgrading JBoss Modules from 1.9.0.Final to 1.9.1.Final · wildfly/wildfly-core@fc649ab · GitHub

So the java.se Java module is no longer added to the runtime options. I see a couple of ways to get past this. One is what Tomaz mentioned in his reply and the other is to just added a dependency on "java.net.http" (Java) module from within your application (either through the use of a jboss-deployment-structure.xml or the "Dependencies" attribute in MANIFEST.MF - more details here Developer Guide )

Having said that, I still don't think these dependencies should be explicitly added. The reason I say this is - the java.net.http.* class are just like any other Java runtime classes and should be available by default to deployments. dmlloyd or brian.stansberry may perhaps have some inputs on this.

[andre.kornetzky]

Thank you both for the helpful answers. The approach with the extension of the MANIFEST.MF seems to be the better way for me.

I am not sure if this is a bug or a feature of the new modularization in JDK9. For an informed answer, I have too little experience with it (just a few weeks).

[ctomc]

Yeah, Jai's answer is better, forgot about the automatic mapping of java modules --> jboss-modules when depending on them.

But in any case, there needs to be a fix applied to WildFly core / jboss-modules to make httpclient by default avalible when running on JDK 11 or newer.

On JDK 9 & 10 http client module was still in "incubating" status and as such was not visible/available by default to user's application. see JEP 321: HTTP Client (Standard)  for details

[jaikiran]

ctomc  wrote:

But in any case, there needs to be a fix applied to WildFly core / jboss-modules to make httpclient by default avalible when running on JDK 11 or newer.

The fix for [MODULES-392] java.se module doesn't take into account all modules that it "requires" - JBoss Issue Tracker  should solve this issue.