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

Phantom messages causing timeout exceptions on ASB

$
0
0
Was directed here via @AzureSupport via Twitter.

When I enable "Break when thrown" in visual studio, I see that timeout exceptions are being thrown by the service bus library I am using (WindowsAzure.ServiceBus 3.4).  Since I only notice when "break when thrown" is enabled, it must be handled within the library, so this is not a fatal exception.

As far as I can tell, there are no pending messages for any of my subscribers, nor any messages in the dead letter queue (this is dev).  I suspect that these messages are for a subscriber that had been deleted and recreated weeks ago.  My concerns are 1) am I doing something wrong (I don't think I am) and 2) in production, under load, would this sort of thing be a problem?

Below are the exception details, except for the endpoint name, which I've replaced with XXXX

System.ServiceModel.FaultException`1 occurred
Message: Exception thrown: 'System.ServiceModel.FaultException`1' in Microsoft.ServiceBus.dll
Additional information: A timeout has occurred during the operation. TrackingId:6e7ee1f8-14c5-40a5-aeb7-998d826e16f1_G25_B23, SystemTracker:XXXX:Topic:user-changed|identity, Timestamp:1/5/2017 3:32:35 PM

Viewing all articles
Browse latest Browse all 1916

Trending Articles



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