-
Bug
-
Resolution: Done
-
Blocker
-
None
-
False
-
None
-
False
-
Regression
-
-
-
-
-
-
-
-
When EAP starts on Windows with SE 17 or later, either via .bat or .ps1, this is written to stdio:
WARNING: package com.sun.net.internal.ssl not in java.base
This is because of a flaw in the JBEAP-25289 fix in common.bat and common.ps1.
Both have a "[S|s]etPackageAvailable" function that runs
java --add-opens=java.base/com.sun.net.ssl.internal.ssl=ALL-UNNAMED -version
with the goal of checking the outcome to detect if the --add-opens is valid, and using that to decide whether to include it in the WF process startup command.
But the check is meant to include searching for 'WARNING' in the output from the java command, and that check is missing. (It's there in the equivalent function in common.sh). The result is the test always evaluates as 'true' and the --add-opens is always part of the command. That leads to warns on SE versions that don't have that package.
The bat function should pipe to findstr and the ps1 function should pipe to Select-String.
- depends on
-
WFCORE-6552 Windows: WARNING: package com.sun.net.internal.ssl not in java.base
- Resolved
- is caused by
-
JBEAP-25289 [GSS](8.0.z) WFCORE-4296 - Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions
- Closed
- is cloned by
-
JBEAP-25828 (7.4.z) WFCORE-6552 - Windows: WARNING: package com.sun.net.internal.ssl not in java.base
- Closed
- is incorporated by
-
JBEAP-25882 (8.0.0) Upgrade WildFly Core from 21.0.3.Final-redhat-00001 to 21.0.4.Final-redhat-00001
- Closed