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
- starts a cluster
start-cluster [--help] [--autohadboverride={true|false}] [--verbose={false|true}] cluster-name
The start-cluster subcommand starts a cluster by starting all GlassFish Server instances in the cluster that are not already running. This subcommand requires secure shell (SSH) to be configured on the host where the domain administration server (DAS) is running and on all hosts where instances in the cluster reside.
Note - If all instances reside on the same host as the DAS, SSH is not required. You might require to start a cluster in which instances reside on hosts where SSH is not configured that are remote from the DAS. In this situation, run the start-local-instance(1) subcommand for each instance from the host where the instance resides.
You may run this subcommand from any host that can contact the DAS.
This subcommand is supported in remote mode only.
Displays the help text for the subcommand.
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.
Specifies whether additional status information is displayed when the cluster is started.
Valid values are as follows:
Displays the command to start each instance in the cluster and whether the attempt to start each instance succeeded.
Displays no additional status information (default).
The name of the cluster to start.
Example 1 Staring a Cluster
This example starts the cluster ymlcluster. Additional status information is displayed when the cluster is started.
asadmin> start-cluster --verbose ymlcluster start-instance yml-i-sr1-usca-02 start-instance yml-i-sr1-usca-01 The command start-instance executed successfully for: yml-i-sr1-usca-02 yml-i-sr1-usca-01 Command start-cluster executed successfully.
command executed successfully
error in executing the command
create-cluster(1), delete-cluster(1), list-clusters(1), setup-ssh(1), start-local-instance(1), stop-cluster(1)