You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to start the Liberty Server in Java 24+ by passing in the JVM argument -Djava.security.manager=allow, the server fails to start because the JVM fails to start.
The messages in the logs looks like:
Server failed to start. Command used to start server was: /home/ci/Build/workspace/ebcTestRunner/dev/autoFVT/image/output/wlp/bin/server
componenttest.exception.TopologyException: Start Server error: The server did not show kernel had started. The server did not show kernel had started. The standard error was: .
Standard out was:
Error occurred during initialization of VM
java.lang.Error: A command line option has attempted to allow or enable the Security Manager. Enabling a Security Manager is not supported.
at java.lang.System.initPhase3(java.base@24-ea/System.java:1947)
.
Return code was: 22.
Message was not found in /home/ci/Build/workspace/ebcTestRunner/dev/autoFVT/image/output/wlp/usr/servers/com.ibm.ws.security.java2sec.fat.earAppJ2SecEnblRestricPerm/logs/console.log
at componenttest.topology.impl.LibertyServer.validateServerStarted(LibertyServer.java:2918)
at componenttest.topology.impl.LibertyServer.startServerWithArgs(LibertyServer.java:1974)
at componenttest.topology.impl.LibertyServer.startServerAndValidate(LibertyServer.java:1515)
at componenttest.topology.impl.LibertyServer.startServerAndValidate(LibertyServer.java:1497)
at componenttest.topology.impl.LibertyServer.startServerAndValidate(LibertyServer.java:1484)
at componenttest.topology.impl.LibertyServer.startServer(LibertyServer.java:1235)
...
The text was updated successfully, but these errors were encountered:
When attempting to start the Liberty Server in Java 24+ by passing in the JVM argument
-Djava.security.manager=allow
, the server fails to start because the JVM fails to start.The messages in the logs looks like:
The text was updated successfully, but these errors were encountered: