[jboss-jira] [JBoss JIRA] (WFLY-12182) Resolve failure with EAP 7.2 mixed domain tests on JDK 12

Resolve failure with EAP 7.2 mixed domain tests on JDK 12 --------------------------------------------------------- Key: WFLY-12182 URL: https://issues.jboss.org/browse/WFLY-12182 Project: WildFly Issue Type: Task Components: Management, Test Suite Reporter: Brian Stansberry Assignee: James Perkins Priority: Major Fix For: 18.0.0.Beta1 The EAP 7.2 mixed domain tests have been failing with JDK 12 since May 1. Task is to figure out why. The changes that went into master before the first failure are here: https://ci.wildfly.org/viewLog.html?buildId=148651&buildTypeId=WF_Mas... Note this includes a WildFly Core upgrade, so that could include all sorts of things. The mixed domain runs report 12 failures, but the non-EAP 7.2 ones looks to be just because the 7.2 problems mess up the test env state, breaking later tests. This is something we've always seen. The failure occurs when starting the legacy Process Controller: {code} &amp#27;[0m05:12:02,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final-redhat-00001 &amp#27;[0m&amp#27;[33m05:12:02,692 WARN [org.jboss.modules.define] (main) Failed to define class org.jboss.logging.MDC in Module "org.jboss.logging" version 3.3.2.Final-redhat-00001 from local module loader @2ddc9a9f (finder: local module finder @298a5e20 (roots: /store/work/tc-work/8edf911abfd02209/testsuite/mixed-domain/target/domains/MixedDomain720TestSuite/slave/added-modules,/store/work/tc-work/8edf911abfd02209/testsuite/mixed-domain/target/domains/MixedDomain720TestSuite/added-modules,/store/work/tc-work/8edf911abfd02209/testsuite/mixed-domain/target/old-versions/jboss-eap-7.2.0/modules,/store/work/tc-work/8edf911abfd02209/testsuite/mixed-domain/target/old-versions/jboss-eap-7.2.0/modules/system/layers/base)): org.jboss.modules.ModuleLoadError: java.se at org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:74) at org.jboss.modules.Module.getPathsUnchecked(Module.java:1608) at org.jboss.modules.Module.loadModuleClass(Module.java:726) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) 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) at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:423) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:519) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126) at org.jboss.modules.Module.loadModuleClass(Module.java:731) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) 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) at org.jboss.as.process-controller@6.0.11.Final-redhat-00001//org.jboss.as.process.Main.start(Main.java:80) at org.jboss.as.process-controller@6.0.11.Final-redhat-00001//org.jboss.as.process.Main.main(Main.java:76) at org.jboss.modules.Module.run(Module.java:352) at org.jboss.modules.Module.run(Module.java:320) at org.jboss.modules.Main.main(Main.java:593) &amp#27;[0mException in thread "main" org.jboss.modules.ModuleLoadError: java.se at org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:74) at org.jboss.modules.Module.getPathsUnchecked(Module.java:1608) at org.jboss.modules.Module.loadModuleClass(Module.java:726) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) 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) at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:423) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:519) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126) at org.jboss.modules.Module.loadModuleClass(Module.java:731) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) 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) at org.jboss.as.process-controller@6.0.11.Final-redhat-00001//org.jboss.as.process.Main.start(Main.java:80) at org.jboss.as.process-controller@6.0.11.Final-redhat-00001//org.jboss.as.process.Main.main(Main.java:76) at org.jboss.modules.Module.run(Module.java:352) at org.jboss.modules.Module.run(Module.java:320) at org.jboss.modules.Main.main(Main.java:593) {code} I'm labeling this a Task for now rather than a Bug because I suspect the problem may be in the test infrastructure. In particular I recommend having a look at anything that changed in the WF Core launcher module in the 9.0.0.Beta4 release. The mixed domain tests use DomainLifecycleUtil, which in turn uses launcher's DomainCommandBuilder. Those use java.lang.Process to start a legacy PC using the JDK 11 jvm on the CI server. So the PC process is completely separate from the test client or the master PC/HC/servers. No reason the old code should stop working with JDK 11 so I suspect something has changed with the launcher. [~jamezp] [~ropalka] FYI