[JBoss JIRA] (WFLY-12182) Resolve failure with EAP 7.2 mixed domain tests on JDK 12
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12182?page=com.atlassian.jira.plugin... ]
James Perkins edited comment on WFLY-12182 at 6/10/19 5:03 PM:
---------------------------------------------------------------
It does look like we could add a workaround as well by adding a {{-Dextra.server.jvm.args=--add-modules=java.se}} property. This worked for me locally at least. Sorry I spoke too soon. This only works for 7.2.0 tests for some reason, but it's something we can likely figure out a way to workaround.
This obviously won't work when Java 8 is used so this is an unusable workaround.
was (Author: jamezp):
It does look like we could add a workaround as well by adding a {{-Dextra.server.jvm.args=--add-modules=java.se}} property. This worked for me locally at least. Sorry I spoke too soon. This only works for 7.2.0 tests for some reason, but it's something we can likely figure out a way to workaround.
> 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: Yeray Borges
> Priority: Major
>
> 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_MasterL...
> 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}
> [0m05:12:02,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final-redhat-00001
> [0m[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)
> [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
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-12182) Resolve failure with EAP 7.2 mixed domain tests on JDK 12
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12182?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-12182:
--------------------------------------
I can confirm that this would fix it https://github.com/wildfly/wildfly-core/compare/master...jamezp:WFLY-12182.
> 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: Yeray Borges
> Priority: Major
>
> 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_MasterL...
> 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}
> [0m05:12:02,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final-redhat-00001
> [0m[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)
> [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
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4154) kie-dmn-core: PMMLInfo NPE when model has zero outputs
by Michael Anstis (Jira)
Michael Anstis created DROOLS-4154:
--------------------------------------
Summary: kie-dmn-core: PMMLInfo NPE when model has zero outputs
Key: DROOLS-4154
URL: https://issues.jboss.org/browse/DROOLS-4154
Project: Drools
Issue Type: Bug
Components: dmn engine
Affects Versions: 7.23.0.Final
Reporter: Michael Anstis
Assignee: Matteo Mortari
Attachments: model-2.pmml, model-3.pmml, model-4.pmml, model.pmml
During testing of the WB changes for PMML support [~jomarko] found the example PMML files referenced by our KIE documentation failed to have a number of models listed against their document definition.
On examination {{PMMLInfo.from(..)}} throws a NPE if the PMML model lacks an _output_ (see L#57 that throws the NPE if the model has a {{null}} _output_). I've attached the files [~jomarko] used for his testing.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4154) kie-dmn-core: PMMLInfo NPE when model has null output
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4154?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-4154:
-----------------------------------
Summary: kie-dmn-core: PMMLInfo NPE when model has null output (was: kie-dmn-core: PMMLInfo NPE when model has zero outputs)
> kie-dmn-core: PMMLInfo NPE when model has null output
> -----------------------------------------------------
>
> Key: DROOLS-4154
> URL: https://issues.jboss.org/browse/DROOLS-4154
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.23.0.Final
> Reporter: Michael Anstis
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: model-2.pmml, model-3.pmml, model-4.pmml, model.pmml
>
>
> During testing of the WB changes for PMML support [~jomarko] found the example PMML files referenced by our KIE documentation failed to have a number of models listed against their document definition.
> On examination {{PMMLInfo.from(..)}} throws a NPE if the PMML model lacks an _output_ (see L#57 that throws the NPE if the model has a {{null}} _output_). I've attached the files [~jomarko] used for his testing.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4154) kie-dmn-core: PMMLInfo NPE when model has null output
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4154?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-4154:
-----------------------------------
Attachment: model.pmml
model-2.pmml
model-3.pmml
model-4.pmml
> kie-dmn-core: PMMLInfo NPE when model has null output
> -----------------------------------------------------
>
> Key: DROOLS-4154
> URL: https://issues.jboss.org/browse/DROOLS-4154
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.23.0.Final
> Reporter: Michael Anstis
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: model-2.pmml, model-3.pmml, model-4.pmml, model.pmml
>
>
> During testing of the WB changes for PMML support [~jomarko] found the example PMML files referenced by our KIE documentation failed to have a number of models listed against their document definition.
> On examination {{PMMLInfo.from(..)}} throws a NPE if the PMML model lacks an _output_ (see L#57 that throws the NPE if the model has a {{null}} _output_). I've attached the files [~jomarko] used for his testing.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-12182) Resolve failure with EAP 7.2 mixed domain tests on JDK 12
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12182?page=com.atlassian.jira.plugin... ]
James Perkins edited comment on WFLY-12182 at 6/10/19 3:21 PM:
---------------------------------------------------------------
It does look like we could add a workaround as well by adding a {{-Dextra.server.jvm.args=--add-modules=java.se}} property. This worked for me locally at least. Sorry I spoke too soon. This only works for 7.2.0 tests for some reason, but it's something we can likely figure out a way to workaround.
was (Author: jamezp):
It does look like we could add a workaround as well by adding a {{-Dextra.server.jvm.args=--add-modules=java.se}} property. This worked for me locally at least.
> 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: Yeray Borges
> Priority: Major
>
> 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_MasterL...
> 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}
> [0m05:12:02,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final-redhat-00001
> [0m[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)
> [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
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-12182) Resolve failure with EAP 7.2 mixed domain tests on JDK 12
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12182?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-12182:
--------------------------------------
It does look like we could add a workaround as well by adding a {{-Dextra.server.jvm.args=--add-modules=java.se}} property. This worked for me locally at least.
> 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: Yeray Borges
> Priority: Major
>
> 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_MasterL...
> 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}
> [0m05:12:02,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final-redhat-00001
> [0m[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)
> [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
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-12182) Resolve failure with EAP 7.2 mixed domain tests on JDK 12
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-12182?page=com.atlassian.jira.plugin... ]
James Perkins commented on WFLY-12182:
--------------------------------------
My guess is that it's related to WFCORE-4415. The PR removed the {{--add-modules=java.se}} in several places including the launcher. Since the current launcher would be used and the older versions of the {{jboss-modules.jar}} likely don't automatically add the {{java.se}} module we should still have the launcher add this property as it should work with any version of WildFly.
> 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: Yeray Borges
> Priority: Major
>
> 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_MasterL...
> 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}
> [0m05:12:02,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final-redhat-00001
> [0m[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)
> [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
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-12182) Resolve failure with EAP 7.2 mixed domain tests on JDK 12
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-12182:
---------------------------------------
Summary: 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: Yeray Borges
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_MasterL...
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}
[0m05:12:02,434 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.6.Final-redhat-00001
[0m[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)
[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
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month