Jump to: navigation, search

settings Section



     


esp-proc-timeout

Default Value: 60
Valid Values: 5-3600
Changes Take Effect: After restart


Specifies the length of time, in seconds, to process ESP requests received by the server. A negative ESP response is returned to a requester if the request is not processed in the specified time.

hide-attached-data

Default Value: true
Valid Values: true, false
Changes Take Effect: After restart


Specifies whether the log file hides (true) or shows (false) attached data for requests to Interaction and Chat Servers.

logging-filter-active

Default Value: false
Valid Values: true, false
Changes Take Effect: After restart


Specifies whether regular expression-based filtering of logging is on (true) or off (false).

logging-filter-spec

Default Value: logging-filter-default.json
Valid Values: logging-filter-default.json
Changes Take Effect: After restart


Specifies the file, which contains filters used in regular expression-based filtering of logging.

logging-max-message-size

Default Value: 5000
Valid Values: 100-1000000
Changes Take Effect: After restart


Specifies the maximum length of logging record.

redis-client-config

Default Value: redisson-config-file.yaml
Valid Values: redisson-config-file.yaml
Changes Take Effect: After restart
Introduced: 9.1.007.05

Specifies the file, which contains the Redis client configuration.

server-mode

Default Value: single

Valid Values:

  • single: The regular operational mode as a single server with primary/backup configuration.
  • dispatcher: The "dispatcher" operational mode.
  • worker: The "worker" operational mode.


Changes Take Effect: After restart
Introduced: 9.1.007.05

Specifies the server operational mode.

session-chat-request-timeout

Default Value: 40
Valid Values: 10-600
Changes Take Effect: After restart


Specifies, in seconds, the timeout value assigned to requests sent to Chat Server: Register, Join, SendMessage. If the timeout expires for a request, then

  • for Register and Join requests—an attempt to create a chat session will be repeated 3 times.
  • for a SendMessage request—an attempt to send a message to a chat session will be repeated 3 times.
  • if all attempts to send a request to Chat Server fail, then an error message will be sent to a channel.

If the timeout expires for a request, then:

  • for Register and Join requests - an attempt to create a chat session will be repeated three times
  • for SendMessage request - an attempt to send a message to a chat session will be repeated three times
  • If all attempts to send a request to Chat Server will fail, then an error message will be sent to a channel.

session-init-number

Default Value: 500
Valid Values: Any integer from 0 to 15000
Changes Take Effect: After restart


Specifies the initial number of simultaneously active chat sessions.

session-max-number

Default Value: 500
Valid Values: 0-15000
Changes Take Effect: After restart


Specifies the maximum number of simultaneous chat sessions to be processed by the server.

session-shutdown-timeout

Default Value: 180
Valid Values: 30-1728000
Changes Take Effect: After restart


Specifies the length of time, in seconds, that will pass before an active chat session is terminated by the server. The session is terminated if, during this time span, there are no inbound or outbound messages and the chat events NewPartyInfo (a new party joined the chat) and PartyLeftInfo (a party left the chat) are not received.

subject-size

Default Value: 25
Valid Values: Any integer: 12-80
Changes Take Effect: After restart


Specifies the maximum size (number of characters) of the subject string for an inbound message. The subject string is created by truncating the inbound message body to the specified length.

workspace-location

Default Value: ./
Valid Values: Valid location in a file system
Changes Take Effect: After restart


Specifies the location of a dedicated folder that can be used by a channel driver to store its data. The folder should have create, write, and read access rights. It may be located somewhere in a network file system.

This page was last edited on July 20, 2018, at 17:05.
Comments or questions about this documentation? Contact us for support!