2.6.23 start-servers
The start-servers subcommand starts all the servers in a batch.
Synopsis
asadmin [asadmin_options] start-servers
Storage location
Application Server installation directory/javaee/glassfish/bin
Function
The start-servers subcommand starts, in a batch, all the servers in the domain. If there is a dependency relation set between servers, the depended-on destination server is started first. If there are many dependency relations, the servers are started in order from the server at the highest-level of the dependency tree. If no dependency is set between the servers, the subcommand processes all the servers simultaneously.
The processing to start the server is not performed for a server that is already running.
This subcommand is supported only in the remote mode.
When the log identifier is changed from default and the --sync=full option is specified in the start-instance subcommand, the following files which are displayed in Node root directory/Node name/Java EE server name/config are deleted because Java EE server restarts. Therefore, create a backup of these files before running this subcommand.
-
The thread dump log of server instance (Default log identifier is javacore)
-
Memory dump (Default log identifiers are core, .core, and *.dmp)
-
Error report file (Default log identifier is hs_err_pid)
-
Compiler replay file (Default log identifier is replay_pid
Execution permission
General user
Precondition
Various servers have been set up.
Examples
The following example starts all the servers in the domain:
asadmin start-servers
Exit Status
Exit Status |
Explanation |
---|---|
0 |
Normal termination. |
1 |
Abnormal termination. |