Please note that the receive timeout might fire and enqueue the ReceiveTimeout message right after another message was enqueued; hence it is not guaranteed that upon reception of the receive timeout there must have been an idle period beforehand as configured via this method.
Once set, the receive timeout stays in effect (i.e. continues firing repeatedly after inactivity periods). Pass in null to switch off this feature.
protected void SetReceiveTimeout( Nullable<TimeSpan> timeout )
member SetReceiveTimeout : timeout : Nullable<TimeSpan> -> unit