4.34. Deprecated Options

4.34.1. resolver_active_source_interval (context)

Interval between sending Topic Resolution advertisements for active sources. A value of 0 indicates that periodic advertisements should not be sent (sources will still respond to queries). NOTE: when set to 0, the resolver_active_threshold should typically also be set to 0. See also Disabling Aspects of Topic Resolution. NOTE: Although this option is eligible to be set during operation, two considerations exist.

• If this option is disabled at initialization (set to 0), you cannot re-set the option during operation.

• Disabling this option by setting it to 0 (zero) during operation prevents you from re-setting the option a second time during operation.

4.34.2. resolver_active_threshold (context)

Number of seconds since the last application message was sent to a source that causes that source to be marked inactive. Inactive sources are not advertised periodically (but will continue to respond to queries). A value of 0 indicates that sources will advertise periodically regardless of how often the application sends messages. Note that for publishers with large numbers of sources, this can increase the topic resolution traffic load. However, also note that this option SHOULD be set to 0 if periodic advertisements are disabled (by setting resolver_active_source_interval to 0). See also Disabling Aspects of Topic Resolution and Interrelated Configuration Options.

4.34.3. resolver_maximum_advertisements (context)

Maximum number of topics that will be advertised per active source interval. A value of 0 means to advertise all topics.

4.34.4. resolver_maximum_queries (context)

Maximum number of topics that will be queried for per query interval. A value of 0 means to query for all topics that do not have at least one source.

4.34.5. resolver_query_interval (context)

Interval between query transmissions for receivers attempting Topic Resolution. A value of 0 indicates queries should not be sent. See also Disabling Aspects of Topic Resolution. NOTE: Although this option is eligible to be set during operation, two considerations exist.

• If this option is disabled at initialization (set to 0), you cannot re-set the option during operation.

• Disabling this option by setting it to 0 (zero) during operation prevents you from re-setting the option a second time during operation.

4.34.6. resolver_query_max_interval (wildcard_receiver)

This sets the maximum interval between wildcard queries in topic resolution (when used). Only PCRE and regex pattern types can use wildcard queries. A value of 0 indicates wildcard queries should not be sent. UM currently queries a maximum of 250 unique wildcard patterns (receivers). NOTE: Although this option is eligible to be set during operation, two considerations exist.

• If this option is disabled at initialization (set to 0), you cannot re-set the option during operation.

• Disabling this option by setting it to 0 (zero) during operation prevents you from re-setting the option a second time during operation.

4.34.7. resolver_unicast_address (context)

The IP address to send unicast topic resolution messages to. If set to 0.0.0.0 (INADDR_ANY), then topic resolution uses multicast (the default). If set to anything else, then topic resolution messages go to the IP address specified.

4.34.8. resolver_unicast_destination_port (context)

The UDP port to send unicast topic resolution messages to. This is the UDP port used by the UM resolution daemon (lbmrd).

4.34.9. resolver_unicast_port (context)

The local UDP port used for unicast topic resolution messages. The UM resolution daemon (lbmrd) will send unicast topic resolution messages to this UDP port. A value of 0 indicates that UM should pick an open port in the range (resolver_unicast_port_low, resolver_unicast_port_high).

4.34.10. retransmit_message_map_tablesz (source)

The size of the hash table that the source uses to store messages for the retention policy in effect. A larger table means more messages can be stored more efficiently, but takes up more memory. A smaller table uses less memory, but costs more CPU time as more messages are retained. See Configuring Late Join for Large Numbers of Messages for additional information about this option.

4.34.11. transport_datagram_max_size (context)

The maximum datagram size that can be generated by UM. The default value is 8192, the minimum is 400 bytes, and the maximum is 65535.

4.34.12. transport_lbtipc_acknowledgement_interval (receiver)

Period of time between acknowledgement (keepalive) messages sent from the receiver to the IPC source. See also transport_lbtipc_client_activity_timeout. Refer to Receiver Configuration and Transport Sessions and Interrelated Configuration Options for additional information.

4.34.13. transport_lbtipc_client_activity_timeout (source)

The maximum period of inactivity (lack of acknowledgement keepalive messages) from a receiver before the source deletes the receiver from it's active receiver table. The IPC source signals all receivers in it's active receiver's table when it writes new data to the shared memory area. See also transport_lbtipc_acknowledgement_interval. Refer to Source Configuration and Transport Sessions and Interrelated Configuration Options for additional information.

4.34.14. ume_message_map_tablesz (source)

The size of the hash table that the source uses to store messages for the retention policy in effect. A larger table means more messages can be stored more efficiently, but takes up more memory. A smaller table uses less memory, but costs more CPU time as more messages are retained. This setting no longer has any effect.

4.34.15. ume_primary_store_address (source)

IPv4 address of the persistent store to be used as the primary store. A value of 0.0.0.0 (or INADDR_ANY) indicates no store is set as the primary. In other words, persistence is not enabled for the source. This setting is deprecated. Its use is not recommended except by legacy systems. Please use the ume_store option instead.

4.34.16. ume_primary_store_port (source)

TCP port of the primary persistent store. This setting is deprecated. Its use is not recommended except by legacy systems. Please use the ume_store option instead.

4.34.17. ume_registration_id (source)

32-bit value that is used by a persistent store to identify a source. If a source desires to identify itself as a previously known source (after a crash or shutdown), it should set the ID to the value it was using before. A value of 0 indicates the source will allow the persistent store to assign an ID. This setting is deprecated. Its use is not recommended except by legacy systems. Please use the ume_store option instead.

4.34.18. ume_secondary_store_address (source)

IPv4 address of the persistent store to be used as the secondary store. A value of 0.0.0.0 (or INADDR_ANY) indicates no store is set as the secondary. This setting is deprecated. Its use is not recommended except by legacy systems. Please use the ume_store option instead.

4.34.19. ume_secondary_store_port (source)

TCP port of the secondary persistent store. This setting is deprecated. Its use is not recommended except by legacy systems. Please use the ume_store option instead.

4.34.20. ume_tertiary_store_address (source)

IPv4 address of the persistent store to be used as the tertiary store. A value of 0.0.0.0 (or INADDR_ANY) indicates no store is set as the tertiary. This setting is deprecated. Its use is not recommended except by legacy systems. Please use the ume_store option instead.

4.34.21. ume_tertiary_store_port (source)

TCP port of the tertiary persistent store. This setting is deprecated. Its use is not recommended except by legacy systems. Please use the ume_store option instead.