Using the GlassFish Command-Line Commands create-jvm-options or delete-jvm-options Does Not Mark an Instance as Needing Restart (Doc ID 2024688.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle GlassFish Server - Version 3.1.2 and later
Information in this document applies to any platform.

Symptoms

Making a change to a Glassfish configuration's Java options using the asadmin commands create-jvm-options or delete-jvm-options does not mark the instance(s) in the configuration as needing restart:

There is no indication in the admin server's console that the instance needs to be restarted:

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