Used in: cluster-config.
The outgoing-message-handler splits logical messages into packets for transmission on the network, and enqueues them on the packet-publisher.
The following table describes the elements you can define within the outgoing-message-handler element.
Element | Required/Optional | Description |
---|---|---|
<use-daemon> | Required | Specifies whether or not a daemon thread will be created to perform the outgoing message handling.
If the daemon thread is NOT created, then any thread that sends a message will itself do the work of splitting the message into packets and putting them into the packet publisher's queue. This is the recommended value as it spreads the processing over more threads. Legal values are: Legal values are true or false. Default value is false. |
<use-filters> | Optional | Contains the list of filter
names to be used by this outgoing message handler. For example, specifying use-filter as follows <use-filters> <filter-name>gzip</filter-name> </use-filters>
|
<priority> | Required | Specifies a priority of the outgoing message handler execution thread.
Legal values are from 1 to 10. Default value is 7. |
The content override attribute xml-override can be optionally used to fully or partially override the contents of this element with XML document that is external to the base document.