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

High volume of socket/connection/certificate exceptions sending messages to queues/topics in Azure Service Bus

$
0
0

Hi -

Over the past few days we are seeing an increase in issues when sending messages to both queues and topics hosted in Azure Service Bus (not on-prem).

Messages are being sent from App Services in all situations, C#, standard MessagingFactory/QueueClient - this code has been running in production and unchanged for months.  We typically have seen these errors sporadically in the past, and assumed it was a transient thing, but they've been happening with increased frequency in recent days

Three of the exceptions:

1) 

An attempt was made to access a socket in a way forbidden by its access permissionsAn attempt was made to access a socket in a way forbidden by its access permissionsAn attempt was made to access a socket in a way forbidden by its access permissionsAn attempt was made to access a socket in a way forbidden by its access permissions 

2)

2. Could not connect to net.tcp://XXXXXX.servicebus.windows.net:9354/. The connection attempt lasted for a time span of 00:00:00. TCP error code 10013: An attempt was made to access a socket in a way forbidden by its access permissions. Could not connect to net.tcp://XXXXXX.servicebus.windows.net:9354/. The connection attempt lasted for a time span of 00:00:00. TCP error code 10013: An attempt was made to access a socket in a way forbidden by its access permissions. An attempt was made to access a socket in a way forbidden by its access permissions

3)

3. The X.509 certificate CN=servicebus.windows.net is not in the trusted people store. The X.509 certificate CN=servicebus.windows.net chain building failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. A certificate chain could not be built to a trusted root authority. The X.509 certificate CN=servicebus.windows.net is not in the trusted people store. The X.509 certificate CN=servicebus.windows.net chain building failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. A certificate chain could not be built to a trusted root authority. The X.509 certificate CN=servicebus.windows.net is not in the trusted people store. The X.509 certificate CN=servicebus.windows.net chain building failed. The certificate that was used has a trust chain that cannot be verified. Replace the certificate or change the certificateValidationMode. A certificate chain could not be built to a trusted root authority. 

Top of the stack:

Microsoft.ServiceBus.Messaging.MessagingCommunicationException:
   at Microsoft.ServiceBus.Common.AsyncResult.End (Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.RunSynchronously (Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)
   at Microsoft.ServiceBus.Messaging.MessageSender.OnSend (Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)
   at Microsoft.ServiceBus.Messaging.MessageSender.Send (Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)
   at Microsoft.ServiceBus.Messaging.MessageSender.Send (Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)
   at Microsoft.ServiceBus.Messaging.QueueClient.Send (Microsoft.ServiceBus, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)


Viewing all articles
Browse latest Browse all 1916

Trending Articles



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