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

inconsistency in JDK17 JAVA_OPTS in domain.bat and standalone.ps1 scripts

XMLWordPrintable

    • Hide

      Used software versions:
      RHEL8/Windows Server 2019
      openJDK 17.0.1

      Used commands:
      RHEL8

      // setting jdk17 as a default jdk
      ./standalone.sh

      // setting jdk17 as a default jdk
      ./domain.sh

      Windows Server 2019:

      PowerShell:
      // setting jdk17 as a default jdk
      PowerShell -ExecutionPolicy Bypass -File standalone.ps1

      Cmd:
      // setting jdk17 as a default jdk
      domain.bat

      Show
      Used software versions: RHEL8/Windows Server 2019 openJDK 17.0.1 Used commands: RHEL8 // setting jdk17 as a default jdk ./standalone.sh // setting jdk17 as a default jdk ./domain.sh Windows Server 2019: PowerShell: // setting jdk17 as a default jdk PowerShell -ExecutionPolicy Bypass -File standalone.ps1 Cmd: // setting jdk17 as a default jdk domain.bat

      We have a simple test that expects -Djava.security.manager=allow property in JAVA_OPTS of a server started by standalone/domain scripts.

      Standalone.[sh/bat] sets JAVA_OPTS as expected (with -Djava.security.manager=allow) whereas a PowerShell variant does not (please see the attached image).

      The same situation is with domain.bat - it doesn't set the expected security manager parameter as domain.sh one.

      Should we expect the same JAVA_OPTS setting behavior across all these mentioned scripts? Please correct me if I made some incorrect conclusions.

              chaowan@redhat.com Chao Wang
              chaowan@redhat.com Chao Wang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: