14.2.2 ezserver (starts an EADS server in the foreground)

Organization of this subsection

(1) Description
(2) Rules
(3) Format
(4) Options and arguments
(5) Return code
(6) Notes

(1) Description

This command starts an EADS server in the foreground.

To Page Top

(2) Rules

This command can be executed when the EADS server is stopped.
To execute this command, log in to the host on which you plan to start the EADS server. To start all EADS servers in the cluster, you must execute this command for each EADS server.
During command execution, the message logs are output to the console and to eads_server_message[n].log ([n] indicates the sequence number of the file) under the directory specified in the eads.logger.dir parameter in the server properties.

To Page Top

(3) Format

ezserver [-h]
         [-r|-ai EADS-server-ID|-ap EADS-server-location-(hash-value)]
         [-rd port-number suspend-method]

To Page Top

(4) Options and arguments

(a) -h or --help

Specify this option to display the command's usage.

When this option is specified, any other options that are specified are ignored.

(b) -r or --recovery

Specify this option to restore a stopped EADS server into the cluster and set its cluster participation status to online.

(c) -ai EADS-server-ID or --add_id EADS-server-ID

Specify this option if you want to add a new EADS server to a specific range in the existing cluster configuration. Specify in this option the EADS server ID of the EADS server that currently manages the range into which the new EADS server is to be added.

An EADS server ID is an integer in the range from 1 to 96.

The new EADS server will be placed at the midpoint between the two EADS servers (hash values) adjacent to where the new EADS server will be located on the consistent hashing circumference. The smallest integer in the range from 1 to 96 that has not been assigned to any existing EADS servers is assigned as the new EADS server's EADS server ID.

If none of the EADS servers in the cluster has the specified EADS server ID, an error results. An error also results if the cluster contains an isolated or stopped (-----------) EADS server when the command with this option specified is executed.

(d) -ap EADS-server-location-(hash-value) or --add_position EADS-server-location-(hash-value)

Specify this option if you want to add a new EADS server at a specific location (hash value) in the existing cluster configuration. Specify in this option the location (hash value) at which the new EADS server is to be added.

For the location (hash value), you can specify an integer in the range from -2147483648 to 2147483647.

The smallest integer in the range from 1 to 96 that has not been assigned to any existing EADS server is assigned as the new EADS server's EADS server ID.

If the specified location (hash value) is already occupied by an existing EADS server, an error results. An error also results if the cluster contains an isolated or stopped (-----------) EADS server when the command with this option specified is executed.

(e) -rd port-number suspend-method or --remotedebug port-number suspend-method

This option is used to remotely debug user functions by using a debugger application. Do not use this option in a production environment.

Use this option to start the EADS server with the following java options specified:

-agentlib:jdwp=transport=dt_socket,server=y,suspend=suspend-method,address=port-number

For the port number (used by the EADS server to connect to the debugger application), you can specify an integer in the range from 1024 to 65535.

If the EADS server is to be started after it has been connected with the debugger application, specify y for suspend-method. If the EADS server is to be started without waiting to be connected with the debugger application, specify n for suspend-method.

To Page Top

(5) Return code

0: Normal termination

Other than 0: Error

To Page Top

(6) Notes

To execute this command, you must first specify /bin and /usr/bin in the PATH environment variable.
If a number of the EADS servers are started in quick succession in a cluster that consists of many EADS servers, the processing will require some time to complete, and startup might time out. In such a case, start the EADS servers sequentially with enough of an interval between startups of the EADS servers. Alternatively, adjust the eads.admin.boot.timeout parameter value in the server properties.
If you execute this command for a running EADS server, the KDEA08408-E message is output and the processing is canceled. However, if two attempts to start the EADS server are made at almost the same time, the message might not be output. In that case, wait a while, and then try to start the EADS server again.
When you specify the -ai or --add_id option or the -ap or --add_position option, no cluster property file will be needed for the EADS server to be added. If the EADS server to be added already has a cluster property file, that cluster property file will not be imported. No error results if the EADS server to be added has a cluster property file with invalid contents.

To Page Top