Microsoft Azure Service Bus Exceptions

Question

We have an application running on the Microsoft Azure cloud platform. Communication between some components is carried out using the service bus. Everything worked fine, until recently, we started getting the following types of timeout exceptions:

When calling QueueClient x.Send(...)

Exception thrown at [0]: at Microsoft.ServiceBus.Common.AsyncResult.End [TAsyncResult] (IAsyncResult result) in Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.DuplexCorreultsynerReseserultResultReseserviceIult Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory `1.RequestSessionChannel.RequestAsyncResult.b__4 (RequestAsyncResult thisPtr, IAsyncResult r) at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StynCallCall

When calling NamespaceManager x.GetQueue(...)

Error processing the PROGRESS queue. System.TimeoutException: The request expires after 60,000 milliseconds. Successful completion of the request cannot be determined. Additional queries should determine if the operation was successful. TrackingId: bdffb6bd-5367-4573-aaa3-8ea9a03f5a2b, TimeStamp: 5/28/2015 8:39:46 ---> System.Net.WebException: the request was aborted: the request was canceled. in System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult)
at Microsoft.ServiceBus.Messaging.ServiceBusResourceOperations.GetAsyncResult`1.b__49 (GetAsyncResult`1 thisPtr, IAsyncResult r) at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback (IAsyncResult)

When calling NamespaceManager x.SubscriptionExists(...)

Exception performing periodic work: System.TimeoutException: The request expires after 00:10:00 milliseconds. Successful completion of the request cannot be determined. Additional requests must be made to determine if the operation was successful. Server stack trace: Exception thrown at [0]: at Microsoft.ServiceBus.Common.AsyncResult.End [TAsyncResult] (IAsyncResult result) in Microsoft.ServiceBus.NamespaceManager.OnEndSubscriptionExists (IAsyncResult result) in Microsoft.ServiceBergeager. String topicPath, String name) ...

When calling QueueClient x.Receive(...)

Error processing the PROGRESS queue. Microsoft.ServiceBus.Messaging.MessagingCommunicationException: Error while communicating with the service bus. Check the connection information, then try again. ---> System.ServiceModel.CommunicationObjectFaultedException: Internal Server Error: the server did not provide a meaningful response; this may be caused by premature session disconnection. TrackingId: 04ba0220-0350-4806-9c65-c2bba9671054, timestamp: 05/28/2015 13:00:55 Server stack trace: Exception thrown at [0]: at Microsoft.ServiceBus.Common.ExceptionDispatcher.Throw (Exception exception) when Microsoft.ServiceBus.Common.AsyncResult.End [TAsyncResult] (IAsyncResult result) in Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.DuplexCorrelationQlestBentSlestBentSerlestesserestlessesserultessessultultessessultultessessultultessessultultessessultultesserultessessessultessessessultultesservice (IAsyncResult result) in Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.RequestAsyncResult.b__4 (RequestAsyncResult thisPtr, IAsyncResult` .

The exceptions are explicitly related to the ServiceBus, and they are not deterministic. Functions that throw them, for example, Send , GetQueue , SubscriptionExists , are called no more than 100-120 times per minute. We did not change anything in the code and increased the timeout values ​​(even to ridiculously high values, for example 10 minutes) did not help. In addition, we do not believe that this is a network problem (for our part), since the same error occurs when the application is launched from different places.

Has anyone else encountered such exceptions recently? Is there a problem on the Microsoft side or are we missing something?

Answer 1

I had a similar problem when my running code started throwing a Timeout exception. The study found that the firewall blocked the port used for communication. However, ports 80 and 443 were open. Therefore, the following line of code worked for me:

 ServiceBusEnvironment.SystemConnectivity.Mode = ConnectivityMode.Https; 

Answer 2

A few weeks ago, we had unexpected and unexplained problems with delivery times with our Bus Bus service, which has been operating for many months. Ours continued to work, but every few calls took 10 + seconds, when they usually amounted to 100-200 milliseconds. This went on for a couple of weeks, and I spent most of it trying to figure out what was going on and never did, as the problem suddenly disappeared.

We learned that the new Service Bus namespaces that we created in the same and different data centers for testing, while the problem arose, did not reveal the same problem. Service Bus did not offer any help and would say that response time is not guaranteed only by SLAs.