Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-4383

DomainCommandBuilder ignores the specified PC/HC JVM

    XMLWordPrintable

Details

    Description

      The WFCORE-4329 fix results in DomainCommandBuilder ignoring a configured JVM and instead using Jvm.current() for the HC and PC.

      https://github.com/wildfly/wildfly-core/pull/3692/files#diff-86e68a2cbfc652da1a61f3528a6f7fd5R70

      This is the cause of mixed-domain testsuite failures in full when the test driver uses JDK 11. The test's configuring of the PC/HC to use JDK 8 is being ignored.

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4329 The launcher API may incorrectly assume the JVM is a non-modular JVM

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: