storeUserConfig No Longer Works With Newer Java Versions - Hangs after Entering Password
(Doc ID 2376121.1)
Last updated on MARCH 20, 2018
Applies to:Oracle HTTP Server - Version 188.8.131.52.0 and later
Oracle Fusion Middleware - Version 184.108.40.206.0 and later
Oracle WebLogic Server - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
A problem is reported with Oracle HTTP Server (OHS) 18.104.22.168 when storing the Node Manager password for starting OHS. It is suspected to affect other 12c products and versions in the same manner.
You can avoid password every time you start a component with startComponent.sh |.cmd by initially starting it with the storeUserConfig:
$DOMAIN_HOME/bin/startComponent.sh componentName storeUserConfig
startComponent.sh ohs1 storeUserConfig
Starting system Component ohs1 ...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Reading domain from /app/oracle/Middleware/OH1/user_projects/domains/kaba_domain
Please enter Node Manager password:
Creating the key file can reduce the security of your system if it is not kept in a secured location after it is created. Creating new key...
- The problem is here, where the process stalls or hangs
-- Nothing is happening
-- In /home/oracle/.wlst directory, there is only one new file nm-key-base_domain.props with 0 bytes
The expectation is two files generated with domain and password data:
- Recently installed with the latest JDK
- Recently updated the JDK
This was reported with OHS 22.214.171.124 using Java 1.8.0_161, released January 2018. It is suspected to affect other 12c products and versions in the same manner.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!