added to the Service Bus content set

Author: spelluru

articles/event-hubs/event-hubs-messaging-exceptions.md

@@ -100,26 +100,26 @@ ExceptionId: 00000000000-00000-0000-a48a-9c908fbe84f6-ServerBusyException: The r
 ```
 
 ## Connectivity, certificate, or timeout issues
-The following steps may help you with troubleshooting connectivity/certificate/timeout issues to all services under *.servicebus.windows.net. 
+The following steps may help you with troubleshooting connectivity/certificate/timeout issues for all services under *.servicebus.windows.net. 
 
 - Browse to or [wget](https://www.gnu.org/software/wget/) `https://sbwagn2.servicebus.windows.net/`. It helps with checking whether you have IP filtering or virtual network or certificate chain issues (most common when using java SDK).
 - Run the following command to check if any port is blocked on the firewall. Depending on the library you use, other ports are also used. For example: 443, 5672, 9354.
 
-    ```shell
-    tnc sbwagn2.servicebus.windows.net -port 5671 (Powershell)
+    ```powershell
+    tnc sbwagn2.servicebus.windows.net -port 5671
     ```
 
     On Linux:
 
     ```shell
-    telnet sbwagn2.servicebus.windows.net 5671 (linux)
+    telnet sbwagn2.servicebus.windows.net 5671
     ```
-- When there are intermittent connectivity issues, run the following command to check if there's any packets dropped. Keep it running for approximately 1 minute to know if the connections are partially blocked. You can download the `psping` tool from [here](/sysinternals/downloads/psping).
+- When there are intermittent connectivity issues, run the following command to check if there are any dropped packets. Keep it running for approximately 1 minute to know if the connections are partially blocked. You can download the `psping` tool from [here](/sysinternals/downloads/psping).
 
     ```shell
     psping.exe -t -q ehedhdev.servicebus.windows.net:9354 -nobanner     
     ```
-    You can use equivalent commands if you're using other tools `tnc`, `ping`, and so on. 
+    You can use equivalent commands if you're using other tools such as `tnc`, `ping`, and so on. 
 - Obtain a network trace if the previous steps don't help and analyze it or contact [Microsoft Support](https://support.microsoft.com/). 
 
 ## Next steps

articles/service-bus-messaging/TOC.yml

@@ -205,7 +205,7 @@
         href: service-bus-resource-manager-namespace-topic-with-rule.md
   - name: Troubleshoot
     items:
-    - name: Exceptions
+    - name: Troubleshooting guide
       href: service-bus-messaging-exceptions.md
 - name: Reference
   items:

articles/service-bus-messaging/service-bus-messaging-exceptions.md

@@ -1,5 +1,5 @@
 ---
-title: Azure Service Bus messaging exceptions | Microsoft Docs
+title: Troubleshooting guide for Azure Service Bus | Microsoft Docs
 description: List of Service Bus messaging exceptions and suggested actions.
 services: service-bus-messaging
 documentationcenter: na
@@ -17,18 +17,22 @@ ms.date: 09/21/2018
 ms.author: aschhab
 
 ---
-# Service Bus messaging exceptions
-This article lists some exceptions generated by the Microsoft Azure Service Bus messaging APIs. This reference is subject to change, so check back for updates.
 
-## Exception categories
+# Troubleshooting guide for Azure Service Bus
+This article provides some of the .NET exceptions generated by Service Bus .NET Framework APIs and also other tips for troubleshooting issues. 
+
+## Service Bus messaging exceptions
+This section lists the .NET exceptions generated by .NET Framework APIs. 
+
+### Exception categories
 The messaging APIs generate exceptions that can fall into the following categories, along with the associated action you can take to try to fix them. The meaning and causes of an exception can vary depending on the type of messaging entity:
 
 1. User coding error ([System.ArgumentException](https://msdn.microsoft.com/library/system.argumentexception.aspx), [System.InvalidOperationException](https://msdn.microsoft.com/library/system.invalidoperationexception.aspx), [System.OperationCanceledException](https://msdn.microsoft.com/library/system.operationcanceledexception.aspx), [System.Runtime.Serialization.SerializationException](https://msdn.microsoft.com/library/system.runtime.serialization.serializationexception.aspx)). General action: try to fix the code before proceeding.
 2. Setup/configuration error ([Microsoft.ServiceBus.Messaging.MessagingEntityNotFoundException](/dotnet/api/microsoft.azure.servicebus.messagingentitynotfoundexception), [System.UnauthorizedAccessException](https://msdn.microsoft.com/library/system.unauthorizedaccessexception.aspx). General action: review your configuration and change if necessary.
 3. Transient exceptions ([Microsoft.ServiceBus.Messaging.MessagingException](/dotnet/api/microsoft.servicebus.messaging.messagingexception), [Microsoft.ServiceBus.Messaging.ServerBusyException](/dotnet/api/microsoft.azure.servicebus.serverbusyexception), [Microsoft.ServiceBus.Messaging.MessagingCommunicationException](/dotnet/api/microsoft.servicebus.messaging.messagingcommunicationexception)). General action: retry the operation or notify users. Note that the `RetryPolicy` class in the client SDK can be configured to handle retries automatically. See [Retry guidance](/azure/architecture/best-practices/retry-service-specific#service-bus) for more information.
 4. Other exceptions ([System.Transactions.TransactionException](https://msdn.microsoft.com/library/system.transactions.transactionexception.aspx), [System.TimeoutException](https://msdn.microsoft.com/library/system.timeoutexception.aspx), [Microsoft.ServiceBus.Messaging.MessageLockLostException](/dotnet/api/microsoft.azure.servicebus.messagelocklostexception), [Microsoft.ServiceBus.Messaging.SessionLockLostException](/dotnet/api/microsoft.azure.servicebus.sessionlocklostexception)). General action: specific to the exception type; please refer to the table in the following section: 
 
-## Exception types
+### Exception types
 The following table lists messaging exception types, and their causes, and notes suggested action you can take.
 
 | **Exception Type** | **Description/Cause/Examples** | **Suggested Action** | **Note on automatic/immediate retry** |
@@ -57,10 +61,10 @@ The following table lists messaging exception types, and their causes, and notes
 | [TransactionException](https://msdn.microsoft.com/library/system.transactions.transactionexception.aspx) |The ambient transaction (*Transaction.Current*) is invalid. It may have been completed or aborted. Inner exception may provide additional information. | |Retry does not help. |
 | [TransactionInDoubtException](https://msdn.microsoft.com/library/system.transactions.transactionindoubtexception.aspx) |An operation is attempted on a transaction that is in doubt, or an attempt is made to commit the transaction and the transaction becomes in doubt. |Your application must handle this exception (as a special case), as the transaction may have already been committed. |- |
 
-## QuotaExceededException
+### QuotaExceededException
 [QuotaExceededException](/dotnet/api/microsoft.azure.servicebus.quotaexceededexception) indicates that a quota for a specific entity has been exceeded.
 
-### Queues and topics
+#### Queues and topics
 For queues and topics, this is often the size of the queue. The error message property contains further details, as in the following example:
 
 ```Output
@@ -72,7 +76,7 @@ Message: The maximum entity size has been reached or exceeded for Topic: ‘xxx-
 
 The message states that the topic exceeded its size limit, in this case 1 GB (the default size limit). 
 
-### Namespaces
+#### Namespaces
 
 For namespaces, [QuotaExceededException](/dotnet/api/microsoft.azure.servicebus.quotaexceededexception) can indicate that an application has exceeded the maximum number of connections to a namespace. For example:
 
@@ -92,14 +96,36 @@ There are two common causes for this error: the dead-letter queue, and non-funct
     To resolve the issue, read and complete the messages from the dead-letter queue, as you would from any other queue. You can use the [FormatDeadLetterPath](/dotnet/api/microsoft.azure.servicebus.entitynamehelper.formatdeadletterpath) method to help format the dead-letter queue path.
 2. **Receiver stopped**. A receiver has stopped receiving messages from a queue or subscription. The way to identify this is to look at the [QueueDescription.MessageCountDetails](/dotnet/api/microsoft.servicebus.messaging.messagecountdetails) property, which shows the full breakdown of the messages. If the [ActiveMessageCount](/dotnet/api/microsoft.servicebus.messaging.messagecountdetails.activemessagecount) property is high or growing, then the messages are not being read as fast as they are being written.
 
-## TimeoutException
+### TimeoutException
 A [TimeoutException](https://msdn.microsoft.com/library/system.timeoutexception.aspx) indicates that a user-initiated operation is taking longer than the operation timeout. 
 
 You should check the value of the [ServicePointManager.DefaultConnectionLimit](https://msdn.microsoft.com/library/system.net.servicepointmanager.defaultconnectionlimit) property, as hitting this limit can also cause a [TimeoutException](https://msdn.microsoft.com/library/system.timeoutexception.aspx).
 
-### Queues and topics
+#### Queues and topics
 For queues and topics, the timeout is specified either in the [MessagingFactorySettings.OperationTimeout](/dotnet/api/microsoft.servicebus.messaging.messagingfactorysettings) property, as part of the connection string, or through [ServiceBusConnectionStringBuilder](/dotnet/api/microsoft.azure.servicebus.servicebusconnectionstringbuilder). The error message itself might vary, but it always contains the timeout value specified for the current operation. 
 
+## Connectivity, certificate, or timeout issues
+The following steps may help you with troubleshooting connectivity/certificate/timeout issues for all services under *.servicebus.windows.net. 
+
+- Browse to or [wget](https://www.gnu.org/software/wget/) `https://sbwagn2.servicebus.windows.net/`. It helps with checking whether you have IP filtering or virtual network or certificate chain issues (most common when using java SDK).
+- Run the following command to check if any port is blocked on the firewall. Depending on the library you use, other ports are also used. For example: 443, 5672, 9354.
+
+    ```powershell
+    tnc sbwagn2.servicebus.windows.net -port 5671
+    ```
+
+    On Linux:
+
+    ```shell
+    telnet sbwagn2.servicebus.windows.net 5671
+    ```
+- When there are intermittent connectivity issues, run the following command to check if there are any dropped packets. Keep it running for approximately 1 minute to know if the connections are partially blocked. You can download the `psping` tool from [here](/sysinternals/downloads/psping).
+
+    ```shell
+    psping.exe -t -q ehedhdev.servicebus.windows.net:9354 -nobanner     
+    ```
+    You can use equivalent commands if you're using other tools such as `tnc`, `ping`, and so on. 
+- Obtain a network trace if the previous steps don't help and analyze it or contact [Microsoft Support](https://support.microsoft.com/).
 
 
 ## Next steps