Node Manager in Weblogic 12.1.3 (or Later) Does Not Read the Changes in startup.properties File until after Restart (Doc ID 2274572.1)

Last updated on JUNE 28, 2017

Applies to:

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

Symptoms

 In Weblogic 12.1.2 there is a Node Manager running on each host to administer the Domains. Admin server is started by running nmStart('AdminServer'). Some changes are made to the JVM Parameters of the AdminServer via the AdminConsole:

AdminConsole -> Servers -> AdminServer -> ServerStart Tab -> Change JVM Startup Arguments

The changes are reflected in the Startup.properties immediately.

The admin server is then killed via nmKill('AdminServer') and restarted via nmStart('AdminServer')

Using "jps -v" we can verify the new JVM parameters are picked up.

However this has changed with Weblogic 12.1.3 onwards. For example, in Weblogic 12.2.1.1 the startup.properties file still receives the changes made via the admin console, but the changes are not picked up when restarting the AdminServer. The node manager has to be restarted first and then restart the admin server to pick up the changes.

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms