Collapse All Expand All Code: All Code: Multiple Code: C# Code: Visual Basic Code: Visual C++

C#
Visual Basic
Visual C++

Berkeley DB .NET API Documentation
ReplicationConfig..::.RetransmissionRequest Method
ReplicationConfig Class See Also Send Feedback

Set a threshold for the minimum and maximum time that a client waits before requesting retransmission of a missing message.

Namespace: BerkeleyDB
Assembly: libdb_dotnet181 (in libdb_dotnet181.dll) Version: 18.1.32.0

# Syntax

C#
    public void RetransmissionRequest(
    	uint min,
    	uint max
    )

Visual Basic (Declaration)
    Public Sub RetransmissionRequest ( _
    	min As UInteger, _
    	max As UInteger _
    )

Visual C++
    public:
    void RetransmissionRequest(
    	unsigned int min,
    	unsigned int max
    )

#### Parameters

min
  Type: System..::.UInt32
  The minimum number of microseconds a client waits before requesting retransmission.

max
  Type: System..::.UInt32
  The maximum number of microseconds a client waits before requesting retransmission.

# Remarks

If the client detects a gap in the sequence of incoming log records or database pages, Berkeley DB waits for at least min microseconds before requesting retransmission of the missing record. Berkeley DB doubles that amount before requesting the same missing record again, and so on, up to a maximum threshold of max microseconds.

These values are thresholds only. Replication Manager applications use these values to determine when to automatically request retransmission of missing messages. For Base API applications, Berkeley DB has no thread available in the library as a timer, the threshold is only checked when a thread enters the Berkeley DB library to process an incoming replication message. Any amount of time may have passed since the last message arrived and Berkeley DB only checks whether the amount of time since a request was made is beyond the threshold value or not.

By default the minimum is 40000 and the maximum is 1280000 (1.28 seconds). These defaults are fairly arbitrary and the application likely needs to adjust these. The values should be based on expected load and performance characteristics of the master and client host platforms and transport infrastructure as well as round-trip message time.

# See Also

ReplicationConfig Class
BerkeleyDB Namespace