2.6.21 start-instance

Synopsis

asadmin [asadmin-options] start-instance [--help]
    [--debug={false|true}] [--sync={normal|full|none}] instance-name

Storage location

Application Server installation directory/javaee/glassfish/bin

Function

The start-instance subcommand of asadmin starts a server instance. You may run this subcommand from any machine that can contact the DAS. The subcommand can start any server instance, regardless of how the instance was created.

This subcommand is supported in remote mode only.

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

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

Precondition

The remote node where the instance resides must be enabled for remote communication.

Domain Administration Server (DAS) is running.

Arguments

--help | -?

Displays the help text for the subcommand.

--debug={false|true}

Specifies whether the instance is started with Java Platform Debugger Architecture (JPDA) debugging enabled.

Type: Boolean

The following values can be specified:

• true

  The instance is started with JPDA debugging enabled and the port number for JPDA debugging is displayed.

• false

  The instance is started with JPDA debugging disabled. This is the default value.

Default value: false

--sync={normal|full|none}

Specifies the type of synchronization between the DAS and the instance's files when the instance is started.

Type: String

The following values can be specified:

• none

  The DAS does not synchronize the instance's files with any changes. This type of synchronization minimizes the time that is required to start the instance.

• normal

  The DAS synchronizes the instance with changes since the last synchronization as follows:

  For the config directory, the DAS synchronizes the instance with all changes.

  For the applications directory and docroot directory, only a change to a top-level subdirectory causes the DAS to synchronize all files under that subdirectory.

  If a file below a top level subdirectory is changed without a change to a file in the top level subdirectory, full synchronization is required. In normal operation, files below the top level subdirectories of these directories are not changed. If an application is deployed and undeployed, full synchronization is not necessary to update the instance with the change. This is the default value.

• full

  The DAS synchronizes the instance with all the instance files, regardless of whether the files have changed since the last synchronization. This type of synchronization might delay the startup of the instance while the DAS updates all files in the instance directories.

Default value: normal

instance-name

Specifies the name of the server instance to start.

Type: String

The following values can be specified:

• Name of the server instance

Default value: N/A

asadmin start-instance pmdsa1

Exit Status

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