2.6.20 start-cluster

Synopsis

asadmin [asadmin-options] start-cluster [--help]
    [--verbose={false|true}] cluster-name

Storage location

Application Server installation directory/javaee/glassfish/bin

Function

The start-cluster subcommand of asadmin starts a cluster by starting all the server instances in the cluster that are not already running. This subcommand is supported in remote mode only.

When this subcommand is used, there is a timeout period for starting the cluster. If a timeout occurs while starting the cluster or reading the asadmin command, then this subcommand fails to run. However, the start processing of the cluster continues. You can verify whether the cluster has been started successfully, by viewing the KDKD20031-I log or the server instance status in the Administration Console.

Precondition

Distributed Component Object Model (DCOM) remote protocol must be configured on the host where the domain administration server (DAS) is running and on all hosts where instances in the cluster reside. However, if the instances in the cluster are all configured on config-type nodes, then you need not specify DCOM.

Domain Administration Server (DAS) is running.

Arguments

--help | -?

Displays the help text for the subcommand.

--verbose={false|true}

Specifies whether additional status information is displayed when the cluster is started.

Type: Boolean

The following values can be specified:

• true

  Displays the command to start each instance in the cluster and whether the attempt to start each instance succeeded.

• false

  Displays no additional status information. This is the default value.

Default value: false

cluster-name

Specifies the name of the cluster to start.

Type: String

The following values can be specified:

• Name of the cluster

Default value: N/A

asadmin start-cluster --verbose ymlcluster

Exit Status

Exit Status	Explanation
0	command executed successfully.
1	error in executing the command.