My Oracle Support Banner

storeUserConfig No Longer Works With Newer Java Versions - Hangs after Entering Password (Doc ID 2376121.1)

Last updated on SEPTEMBER 07, 2018

Applies to:

Oracle HTTP Server - Version 12.1.3.0.0 and later
Oracle Fusion Middleware - Version 12.1.3.0.0 and later
Oracle WebLogic Server - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

Using the following documentation to configure Oracle HTTP Server with the storeUserConfig tool to start without entering a User and Password to connect to the Node Manager:

Fusion Middleware Administering Oracle Fusion Middleware
Chapter 4 Starting and Stopping Oracle Fusion Middleware
Section 4.3.2.2 Starting and Stopping System Components
https://docs.oracle.com/middleware/12213/lcm/ASADM/starting-and-stopping.htm#GUID-97275D15-1B66-47D0-AC8D-08BD7938BA32

A problem is reported with Oracle HTTP Server (OHS) 12.2.1.3 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

Example:

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...


-- 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:

.wlst/nm-key-base_domain.props
.wlst/nm-cfg-base_domain.props

Changes

Recently installed with the latest JDK or recently updated the JDK.

This was reported with OHS 12.2.1.3 using Java 1.8.0_161, released January 2018.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.