Troubleshooting AMQP Connector | MuleSoft Documentation
# Troubleshooting AMQP Connector
To troubleshoot Anypoint Connector for AMQP (AMQP 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’s interaction with the AMQP Connector is failing, temporarily enable verbose logging for AMQP 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.
  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:
```
			<Loggers>
				...
				<AsyncLogger name="com.mule.extensions.amqp" 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 throw messages and how to interpret them:
  * AMQP:CONNECTIVITY
```
The connection is no longer valid. It is disposed of, but you can apply a reconnection policy if defined in the application setup.
```

  * AMQP:CONSUMING
```
An error occurred while consuming messages and could not be identified.
```

  * AMQP:CREATION_NOT_ALLOWED
```
The queue or exchange does not exist, and the disableCreationOfFallbackQueues or disableCreationOfFallbackExchanges parameters is set.
```

  * AMQP:QUEUE_NOT_FOUND
```
The queue defined does not exist, and no fallbackQueueDefinition is provided.
```

  * AMQP:RETRY_EXHAUSTED
```
The maximum number of retries for the operation is reached.
```

  * AMQP:TIMEOUT
```
The timeout for the requested operation is exceeded.
```

  * AMQP:ILLEGAL_BODY
```
The message body is invalid, for example, a null body.
```

  * AMQP:UNROUTABLE_MESSAGE
```
The message could not be routed, either because it could not be immediately delivered or because there are no queue bounds to the exchange depending on the exchange configuration in the broker.
```

  * AMQP:PUBLISHING
```
An error occurred while publishing messages and could not be identified.
```

  * AMQP:PUBLISHING_CONSUMING
```
A generic error for publishing-consuming, which could not be identified.
```

  * AMQP:EXCHANGE_NOT_FOUND
```
The exchange defined does not exist, and no fallbackExchangeDefinition exists.
```

  * AMQP:EXCHANGE_DECLARATION
```
An exception occurred during an exchange declaration.
```

  * AMQP:BLOCKED_BROKER
```
An error occurred while sending a message because the broker is blocked as it ran out of resources.
```

  * AMQP:ACKNOWLEDGING
```
A generic error for acknowledging, which could not be identified.
```

  * AMQP:DELIVER_TAG_NOT_FOUND
```
The deliver tag to acknowledge was not found by the broker.
```

  * AMQP:REJECTING
```
A generic error for rejecting, which could not be identified.
```

  * AMQP:REQUEUE
```
A generic error on requeue process.
```

  * AMQP:NO_CHANNEL_AVAILABLE
```
A generic error when the channel is not available.
```



## See Also
  * AMQP Connector Reference
  * MuleSoft Help Center
  *