IBM Support

WebSphere Application Server Will Not Start Due to Insufficient Java 2 Security Permissions

Troubleshooting


Problem

IBM WebSphere Application Server instance does not start due to the error "Insufficient Java 2 security permissions" for the file, bootstrap.jar, in the WebSphere Application Server instance's native_stderr.log file.

Symptom

  • Newly created WebSphere Application Server instances do not start
  • The WebSphere Application Server product was recently installed or not used since it was installed
  • The "Insufficient Java 2 security permissions to start the process!" message for bootstrap.jar is logged in the WebSphere Application Server instance's native_stderr.log file after the WebSphere Application Server instance fails to start
Insufficient Java 2 security permissions to start the process!
java.security.policy = /QIBM/UserData/websphere/appserver/v855/express/profiles/uiprod/properties/server.policy
CodeSource for bootstrap.jar = ProtectionDomain  (file:/QIBM/ProdData/Websphere/Appserver/v855/Express/lib/bootstrap.jar <no signer certificates>)
 sun.misc.Launcher$AppClassLoader@97ba67ad
 <no principals>
 java.security.Permissions@1c69b41a (
 ("java.io.FilePermission" "/QIBM/ProdData/Websphere/Appserver/v855/Express/lib/bootstrap.jar" "read")
 ("java.util.PropertyPermission" "java.specification.version" "read")
 ("java.util.PropertyPermission" "java.version" "read")
 ("java.util.PropertyPermission" "os.arch" "read")
 ("java.util.PropertyPermission" "java.specification.vendor" "read")
 ("java.util.PropertyPermission" "java.vm.specification.name" "read")
 ("java.util.PropertyPermission" "java.vm.vendor" "read")
 ("java.util.PropertyPermission" "path.separator" "read")
 ("java.util.PropertyPermission" "os.version" "read")
 ("java.util.PropertyPermission" "file.separator" "read")
 ("java.util.PropertyPermission" "line.separator" "read")
 ("java.util.PropertyPermission" "java.vm.specification.vendor" "read")
 ("java.util.PropertyPermission" "java.specification.name" "read")
 ("java.util.PropertyPermission" "java.vendor.url" "read")
 ("java.util.PropertyPermission" "java.vendor" "read")
 ("java.util.PropertyPermission" "java.vm.version" "read")
 ("java.util.PropertyPermission" "java.vm.name" "read")
 ("java.util.PropertyPermission" "java.vm.specification.version" "read")
 ("java.util.PropertyPermission" "os.name" "read")
 ("java.util.PropertyPermission" "javax.realtime.version" "read")
 ("java.util.PropertyPermission" "java.class.version" "read")
 ("java.lang.RuntimePermission" "exitVM")
 ("java.lang.RuntimePermission" "stopThread")
 ("java.net.SocketPermission" "localhost:0" "listen,resolve")
)

was.install.root = /QIBM/ProdData/websphere/appserver/v855/express
Exception in thread "main" java.lang.RuntimeException: Insufficient Java 2 security permissions to start the process!
    at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:158)

Cause

IBM WebSphere Application Server fails to locate and read product and profile IFS files when the original installation was created with multiple paths with different case sensitivity.  The IBM WebSphere Application Server is sensitive to the case of its was.install.root and was.user.install.root variable values.  When these values do not match the exact case of the paths used by other server property and policy files, the correct Java 2 security permissions cannot be set resulting in the "Insufficient Java 2 security permissions" error for the was.install.root/lib/bootstrap.jar.
Example:
was.install.root = /QIBM/ProdData/websphere/appserver/v855/express
server.policy definition:
("java.io.FilePermission" "/QIBM/ProdData/Websphere/Appserver/v855/Express/lib/bootstrap.jar" "read")
When you compare these two IFS paths, the case sensitivity of these two IFS paths does not match.  As a result, the correct Java 2 security permission is not set and Java 2 security blocks the bootstrap.jar file from being accessed, which is required to start the application server instance successfully.

Environment

IBM WebSphere Application Server
IBM i OS
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Resolving The Problem

To fix the case sensitivity of these WebSphere Application Server product and profile installation paths, the WebSphere Application Server product needs to be uninstalled and reinstalled.  In addition, all WebSphere Application Server profiles created under this installation need to be rebuilt from scratch.  You cannot save and restore profiles under this installation since it carries over the incorrect was.install.root and was.user.install.root variables and other incorrect path references in the various product and profile files.
Information on how to uninstall and reinstall the IBM WebSphere Application Server product on the IBM i OS can be found here:

Document Location

Worldwide

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Component":"WebSphere Application Server","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

Modified date:
27 January 2020

UID

ibm11283992

Page Feedback