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

Details

    • 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

    Description

      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.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-23609 inconsistency in JDK17 JAVA_OPTS in domain.bat and standalone.ps1 scripts

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-5782 Reset java.security.manager default value back to "allow" by default in WildFly shell scripts

          • 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.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: