-
Feature Request
-
Resolution: Done
-
L3 - Default
-
None
-
None
This is the controller panel for Smart Panels app
[CAM-9771] Support Wildfly 16
Beta-upgrade test results:
- Distro unit tests - passing;
- Standard regression test - passing;
- With lots of Warning: Nashorn engine is planned to be removed from a future JDK release messages;
- Webapp IT test - passing;
- Webapp IT test (embedded-engine-rest) - passing (JDK8-10); fails on JDK11 due to WFCORE-3962|JBoss MODULES-372
- Engine IT test (wildfly-servlet) - passing (JDK8-10); fails on JDK11 due to WFCORE-3962|JBoss MODULES-372
- Engine IT test (wildfly-domain) - fails;
Some of the tests are failing when run on JDK11. This is because the java.se module is not included in the set of modules in class path mode by default. A fix has already been provided and should be released in a following beta.
The WildFly Domain tests fail due to a different bug that has been present since the WildFly 15 upgrade (I created CAM-9780 to address the problem).
On starting up the wildfly distribution, the following stacktrace is shown because of a NPE:
10:15:24,351 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."camunda-webapp-ee-jboss-7.11.0-alpha5-ee.war".metrics: org.jboss.msc.service.StartException in service jboss.deployment.unit."camunda-webapp-ee-jboss-7.11.0-alpha5-ee.war".metrics: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NullPointerException at org.wildfly.extension.microprofile.metrics.PrometheusCollector.addMetricFamilySampleSupplier(PrometheusCollector.java:32) at org.wildfly.extension.microprofile.metrics.MetricCollector.collectResourceMetrics0(MetricCollector.java:157) at org.wildfly.extension.microprofile.metrics.MetricCollector.collectResourceMetrics0(MetricCollector.java:166) at org.wildfly.extension.microprofile.metrics.MetricCollector.collectResourceMetrics(MetricCollector.java:92) at org.wildfly.extension.microprofile.metrics.deployment.DeploymentMetricService.start(DeploymentMetricService.java:54) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700) ... 6 more
- This problem cannot be reproduced reliably; It occurs frequently on macOS if the h2 database was cleaned up before.
- With WFLY-11801 there exists a bug issue
- The problem was fixed in Wildfly 17 alpha1
- Since patches are only released for JBoss EAP and not for Wildfly, it is unlikely that Wildfly 16 will be patched
There is an alpha of WildFly 17, we can already create a ticket for it and start testing 
There's a beta available since Wednesday, so we could already try it on a branch (see http://wildfly.org/downloads/).