---
schema_version: "1"
id: ca31314c3565ac801b3c4c24f8b207441f11d78d0d2221b74e87b1a277c1b607
title: Troubleshooting Azure Event Hubs Connector
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/azure-event-hubs-connector/latest/azure-event-hubs-connector-troubleshooting.md
canonical_url: https://docs.mulesoft.com/azure-event-hubs-connector/latest/azure-event-hubs-connector-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: c4da76a504370999e5e2b67737128c6aa6ba241e6028c5a621464a0b27f95874
description: MuleSoft Documentation Site
release: "1.2"
latest: true
---
---
product: Azure Event Hubs Connector
version: 1.2
is-latest-version: true
---

# Troubleshooting Azure Event Hubs Connector

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

To troubleshoot Azure Event Hubs Connector, become familiar with the information about enabling
verbose logging and interpreting commonly thrown messages.

## Enable Verbose Logging

To get a better understanding of why an application is failing, temporarily enable verbose logging
for Azure Event Hubs Connector.

Remember to always disable the enhanced verbosity after troubleshooting because it affects your Mule
application performance.

To enable verbose logging in the configuration file:

1.  Access Anypoint Studio and navigate to the **Package Explorer** view.

2.  Open your application’s project name.

3.  Open the `src/main/resources` path folder.

4.  Open the `log4j2.xml` file inside the folder.

5.  Add an `<AsyncLogger>` tag inside the `<Loggers>` tag:

    ```xml
    			<Loggers>
    				...
    				<AsyncLogger name ="com.azure.messaging.eventhubs.checkpointstore.blob" level= "DEBUG"/>
       <AsyncLogger name="com.azure.messaging.eventhubs" level="DEBUG"/>
       <AsyncLogger name="com.azure.core.amqp" level="DEBUG"/>
       <AsyncLogger name="com.azure.identity" level="DEBUG"/>
    				...
    			</Loggers>
    ```

6.  Save your application changes.

7.  Click the project name in **Package Explorer** and then click **Run** > **Run As** > **Mule
    Application**.

## Understand Common Throws

Here is a list of common throws messages and how to interpret them.

- AZURE-EVENTHUBS:AEH\_ERROR

  An error occurs in Azure Event Hubs.

- AZURE-EVENTHUBS:AUTHENTICATION

  Unable to authenticate to the Azure Event Hubs server.

- AZURE-EVENTHUBS:CONNECTIVITY

  The client became disconnected from the event hub while attempting to publish an event.

- AZURE-EVENTHUBS:INVALID\_INPUT

  The user sent an invalid input.

- AZURE-EVENTHUBS:RETRY\_EXHAUSTED

  The maximum number of retries for the operation is reached.

## See Also

- [Salesforce Help](https://help.salesforce.com)

- [Known Issues](https://help.salesforce.com/s/issues)