Hot Failover (HF) allows your applications to build in sender redundancy. See Hot Failover for a discussion of using Hot Failover within a single receiver context or across multiple receiver contexts.
The interval between periodic forced loss checks. This option defaults to 0, indicating that loss checks should only be made when a new message arrives.
The minimum interval that must expire before the HFX Receiver declares a message unrecoverable and delivers an unrecoverable loss message the application. By default, the HFX Receiver only checks loss when it receives new messages. To enable periodic loss checks, set the delivery_control_loss_check_interval option.
Specifies the largest permissible gap between the next expected message and the most recently received message. When the difference in sequence numbers between the most recently received message and the next expected message exceeds this amount, the HFX Receiver delivers a burst loss notification. The HFX Receiver discards any messages currently pending delivery. Normal delivery resumes with the most recently received message.
The maximum number of map entries for the HFX order and loss maps. This is a soft limit. When the sum of the number of loss records and the number of messages held for ordering (messages that will be delivered once all prior messages have been delivered) is greater than this value, the oldest consecutive sequence of loss records will be declared lost immediately to reduce the number of outstanding map entries. A value of 0 indicates that the map should be allowed to grow without bound.
Flag indicating whether duplicate messages should be discarded or simply marked as duplicates. Setting this to 1 overrides the hf_duplicate_delivery setting on all underlying HFX Receivers.
Flag indicating if the Hot Failover receiver delivers duplicate messages or not.
Indicates if a Hot Failover receiver can receive optional messages. See also Hot Failover Optional Messages.
Specifies whether to create hot failover receivers for each topic that maps to the wildcard receiver pattern.
Flag indicating if the HFX Receiver orders messages before delivery.
| Scope: | hfx |
| Type: | int |
| When to Set: | Can only be set during object initialization. |
| Version: | This option was implemented in LBM 4.2 |
| String value | Integer value | Description |
|---|---|---|
"1" (Integer value as a string.) |
1 |
The HFX Receiver delivers messages in order. Default for all. |
"-1" (Integer value as a string.) |
-1 |
The HFX Receiver delivers messages as soon as they are received. In the case of fragmented messages, as soon as all fragments have been received and reassembled. |
Copyright (c) 2004 - 2014 Informatica Corporation. All rights reserved.