Ultra Messaging® Configuration Guide
Prev	Chapter 4. Reference	Next

4.21. Off-Transport Recovery Options

See also Off-Transport Recovery (OTR) for more information about this feature.

4.21.1. otr_request_duration (receiver)

The length of time a receiver continues to send OTR lost-message requests before giving up.

Scope:	receiver
Type:	lbm_ulong_t
Units:	milliseconds
Default value:	20000 (20 seconds)
When to Set:	Can only be set during object initialization.
Version:	This option was implemented in UM 5.2

4.21.2. otr_request_initial_delay (receiver)

The length of time a receiver waits before initiating OTR lost-message requests.

Scope:	receiver
Type:	lbm_ulong_t
Units:	milliseconds
Default value:	10000 (10 seconds)
When to Set:	Can only be set during object initialization.
Version:	This option was implemented in UM 5.3

4.21.3. otr_request_log_alert_cooldown (receiver)

Each OTR request generates a log message. The first request's log message is a WARNING-level log message, and subsequent requests that quickly follow generate INFO-level log messages. After a time interval defined by this option, the next request leading a new burst of requests again generates a WARNING-level log message.

Scope:	receiver
Type:	lbm_ulong_t
Units:	seconds
Default value:	300 (5 minutes)
When to Set:	Can only be set during object initialization.
Version:	This option was implemented in UM 5.3

4.21.4. otr_request_maximum_interval (receiver)

The maximum time interval between a receiver's OTR lost-message requests. After the receiver initiates OTR and is waiting to receive the retransmission, the initial interval (set by otr_request_minimum_interval) doubles in length for each request until it reaches this option's value, then continues at this interval (until timeout or UM recovers messages). NOTE: When using TCP Request/Response, this value must be shorter than response_tcp_deletion_timeout.

Scope:	receiver
Type:	lbm_ulong_t
Units:	milliseconds
Default value:	10000 (10 seconds)
When to Set:	Can only be set during object initialization.
Version:	This option was implemented in UM 5.3

4.21.5. otr_request_minimum_interval (receiver)

The initial time interval between a receiver's OTR lost-message requests. While the receiver is waiting to receive the retransmission, the interval doubles in length for each request until it reaches the maximum interval set by otr_request_maximum_interval.

Scope:	receiver
Type:	lbm_ulong_t
Units:	milliseconds
Default value:	1000 (1 second)
When to Set:	Can only be set during object initialization.
Version:	This option was implemented in UM 5.2

4.21.6. otr_request_outstanding_maximum (receiver)

The maximum number of OTR lost-message requests outstanding at any given time. Each message specifies an individual lost message. A value of 0 indicates no maximum.

Scope:	receiver
Type:	lbm_ulong_t
Units:	messages
Default value:	200
When to Set:	Can only be set during object initialization.
Version:	This option was implemented in UM 5.2

4.21.7. use_otr (receiver)

Flag indicating if the receiver can use OTR or not.

Scope:	receiver
Type:	int
When to Set:	Can only be set during object initialization.
Version:	This option was implemented in UM 5.2

Value	Description
1	The receiver is enabled to use OTR to recover lost messages.
0	The receiver is not enabled to use OTR to recover lost messages. Default for all.

Prev	Home	Next
Late Join Options	Up	Request Network Options