Quantcast
Channel: Service Bus forum
Viewing all articles
Browse latest Browse all 1916

Daily transient errors received through the message pump with built-in retry policy. Why?

$
0
0

I've been monitoring the exceptions received through the message pump for transient errors and I get daily MessagingCommunicationExceptions. This article (can't post the link...)(Updated: September 16, 2014), recommend the following :

This exception signals a communication error that can manifest itself when a connection from the messaging client to the Service Bus infrastructure cannot be successfully established. In most cases, provided network connectivity exists, this error can be treated as transient. The client can attempt to retry the operation that has resulted in this type of exception. It is also recommended that you verify whether the domain name resolution service (DNS) is operational as this error may indicate that the target host name cannot be resolved.

My understanding is that there is no extra code to write to handle transients errors on the Service Bus after version 2.1 (2013). Unless my premise is wrong, why am I receiving transients errors each and every day? Should exceptions received through the message pump be ignored?

Version of Microsoft.ServiceBus is 2.4.0.0

_queueClient = QueueClient.CreateFromConnectionString(
    _appSettings.ServiceBusConnectionString,
    _appSettings.ServiceBusPath,
    ReceiveMode.ReceiveAndDelete);

var options = new OnMessageOptions();
options.AutoComplete = true;
options.ExceptionReceived += OnExceptionReceived;
options.MaxConcurrentCalls = 1;

_queueClient.OnMessage(OnMessage, options);




Viewing all articles
Browse latest Browse all 1916

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>