Session Communication 

Use

This is a direct connection between dispatcher and server in one cluster group. It is used for faster procession of client requests.

Note that this connection is only used between dispatcher and server in one cluster group. You cannot use this connection for server-to-server communication, or for communication between elements belonging to different cluster groups. In such cases you have to use a Message Server Communication.

Features

The session communication has only one-way operations – from dispatcher to server.

There is a so-called “pure send”, in which the service calling method is returned immediately and the message is placed in a queue where it waits for procession.

Another way of sending messages is the “send in queue” way, in which the calling method is locked until the server receives the message and sends an internal confirmation, or until the timeout, set before sending the message, expires. This model is developed to prevent the parts of one message that is fragmented to several small messages, to miss each other.

 

See also:

Configuring the Session Communication in the Administration Manual