-
Bug
-
Resolution: Done
-
Blocker
-
None
-
False
-
None
-
False
-
-
-
-
-
-
Rejected
-
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.
- is cloned by
-
WFCORE-5920 inconsistency in JDK17 JAVA_OPTS in domain.bat and standalone.ps1 scripts
- Closed