Property

Description

Default Value

barrier.dependent

Determines if the startup and shutdown barriers are dependent. If the property value is "true", there can be only one starting or stopping element in the box/cluster at the moment. If it is "false", there can be only one starting and one stopping element.

false

barrier.shutdown

Determines the serialization kind of the element's shutdown (similar to barrier.startup).

none

barrier.startup

Determines the serialization kind of the element's startup. The following values are available: "none" – no serialization; "box" – serialization in the boundaries of the box, that is, the nodes in one box will be started one by one; "cluster" – serialization in the boundaries of the whole cluster.

none

barrier.timeout

An integer that specifies a timeout in milliseconds. Within this timeout, the element is forced to recheck if it can pass the barrier.

The system uses this property for optimization purposes only. We do not recommend that you change it.

10000

element.clusterId

This parameter specifies the identification number of a cluster element (dispatcher). The ID is unique for the cluster.

5001

element.groupId

Specifies the group ID of the element. The group ID value must be greater than zero.

1

element.name

Specifies the name of the cluster element (dispatcher).

Dispatcher One

element.type

Specifies the type of the cluster element (server or dispatcher).

dispatcher

ms.host

This is the host (IP address), where the Message Server is running.

localhost

ms.message.pool.size

Defines the size of the message library pool. The size of this pool can be changed for optimization purposes.

10000

ms.port

This is the port on which the Message Server listens for connections.

3604

session.message.queue.size

Defines the size of the session layer queue. The size of this queue can be changed for optimization purposes.

256

socket.SO_KEEPALIVE

Enables and disables the socket “keep alive” option. This property has a Boolean value. If it is false, the socket “keep alive” option is disabled.

false

socket.SO_LINGER

Enables and disables a socket linger with the specified time in seconds. The maximum timeout value is platform specific.

“-1” implies that the option is disabled. The setting only affects the socket close.

-1

socket.SO_RCVBUF

Sets the received buffer size for this socket.

This property has the same use as the socket.SO_SNDBUF property described above.

65536

socket.SO_SNDBUF

Sets the send buffer size for this socket. This option is used by the platform's networking code as a hint for the size to set the underlying network I/O buffers.

Increasing the buffer size can increase the performance of network I/O for high-volume connection, while decreasing it can help reduce the backlog of incoming data.

65536

socket.SO_TIMEOUT

Enables and disables the socket timeout with the specified value in milliseconds. The timeout must be > 0. A timeout of zero is interpreted as an infinite timeout, that is, the timeout is disabled.

0

socket.TCP_NODELAY

This property takes a Boolean value that specifies whether Nagle’s algorithm is disabled or enabled for this socket. Setting socket.TCP_NODELAY to “true” improves system performance, especially if multiple small portions of data are sent through the socket.

true

Property

Description

Default Value

barrier.dependent

See above.

false

barrier.shutdown

See above.

none

barrier.startup

See above.

none

barrier.timeout

See above.

10000

element.clusterId

See above.

4001

element.groupId

See above.

1

element.joinPort

The server listens for connections on this port.

2078

element.name

See above.

Server One

element.type

See above.

server

lazy.autoclose.timeout

Specifies the time through which the lazy connection will be open after the last large group of message is transported. After this timeout the Cluster Manager closes the connection.

The time is in milliseconds. The maximum for closing a socket is between 5 and 10 seconds.

5000

lazy.message.pool.size

Specifies the size of the pool where the currently unused message objects are stored. This message objects are used by the messaging system for internal use only.

The value must be equal or greater than “0”.

10000

lazy.threshold

Specifies the size of the messages that must be sent during a time interval equal to the value set in the lazy.time.piece property.

The value must be equal or greater than “0”. If the value is “0”, all messages will be transferred through a lazy connection.

1048576

lazy.time.piece

Specifies the time interval in milliseconds for which the quantity of messages defined by the lazy.threshold property have to be exchanged between two parties in order to open a lazy connection.

If two parties open a connection and succeed in exchanging more messages than the size defined by the lazy.threshold property for the time defined in this property, then a lazy connection will be opened.

ms.host

See above.

localhost

ms.message.pool.size

See above.

10000

ms.port

See above.

3604

session.message.queue.size

See above.

256

socket.SO_KEEPALIVE

See above.

false

socket.SO_LINGER

See above.

-1

socket.SO_RCVBUF

See above.

65536

socket.SO_SNDBUF

See above.

65536

socket.SO_TIMEOUT

See above.

0

socket.TCP_NODELAY

See above.

True