Oracle GlassFish Server 3.1 Section 1: asadmin Utility Subcommands
create-connector-connection-pool(1)
create-connector-security-map(1)
create-connector-work-security-map(1)
create-jdbc-connection-pool(1)
create-message-security-provider(1)
create-resource-adapter-config(1)
delete-connector-connection-pool(1)
delete-connector-security-map(1)
delete-connector-work-security-map(1)
delete-jdbc-connection-pool(1)
delete-message-security-provider(1)
delete-resource-adapter-config(1)
disable-http-lb-application(1)
disable-secure-admin-internal-user(1)
disable-secure-admin-principal(1)
enable-secure-admin-internal-user(1)
enable-secure-admin-principal(1)
list-connector-connection-pools(1)
list-connector-security-maps(1)
list-connector-work-security-maps(1)
list-message-security-providers(1)
list-resource-adapter-configs(1)
list-secure-admin-internal-users(1)
list-secure-admin-principals(1)
list-supported-cipher-suites(1)
unfreeze-transaction-service(1)
update-admin-server-coordinates(1)
update-admin-server-local-coordinates(1)
update-connector-security-map(1)
update-connector-work-security-map(1)
Oracle GlassFish Server 3.1 Section 1M: Utility Commands
Oracle GlassFish Server 3.1 Section 5ASC: GlassFish Server Concepts
- stops a GlassFish Server cluster
stop-cluster [--help] [--verbose={false|true}] [--kill={false|true}] [--autohadboverride={true|false}] cluster-name
The stop-cluster subcommand stops a GlassFish Server cluster by stopping all running GlassFish Server instances in the cluster.
This subcommand is supported in remote mode only.
Displays the help text for the subcommand.
Specifies whether additional progress messages about the status of instances in the cluster are displayed while the cluster is being stopped.
Possible values are as follows:
Additional progress messages about the status of instances in the cluster are displayed.
No messages about the status of instances in the cluster are displayed.
Specifies whether each instance in the cluster is killed by using functionality of the operating system to terminate the instance process.
Possible values are as follows:
No instances are killed. The subcommand uses functionality of the Java platform to terminate each instance process (default).
Each instance is killed. The subcommand uses functionality of the operating system to terminate each instance process.
Do not specify this option. This option is retained for compatibility with earlier releases. If you specify this option, a syntax error does not occur. Instead, the subcommand runs successfully and displays a warning message that the option is ignored.
The name of the cluster to stop.
Example 1 Stopping a Cluster
This example stops the cluster pmdcluster. Additional progress messages about the status of instances in the cluster are displayed while the cluster is being stopped.
asadmin> stop-cluster --verbose pmdcluster stop-instance pmd-i-sj01 stop-instance pmd-i-sj02 The command stop-instance executed successfully for: pmd-i-sj01 pmd-i-sj02 Command stop-cluster executed successfully.
command executed successfully
error in executing the command
create-cluster(1), delete-cluster(1), list-clusters(1), start-cluster(1)