---
schema_version: "1"
id: 62d0a07b0105cc1e18822a19d367665b56f703cd1c489ed55bb8d76bdd659618
title: Troubleshooting VM Connector
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/vm-connector/latest/vm-connector-troubleshooting.md
canonical_url: https://docs.mulesoft.com/vm-connector/latest/vm-connector-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 4b88aa7f119f04ad30f2dca43105a95daa0b81a275f16c3fa8927991204a43e5
description: MuleSoft Documentation Site
release: "2.0"
latest: true
---
---
product: VM Connector
version: 2.0
is-latest-version: true
---

# Troubleshooting VM Connector

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

To troubleshoot Anypoint Connector for Virtual Machine (VM 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 VM Connector is failing,
temporarily enable verbose logging for VM 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="org.mule.extensions.vm" 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:

- VM:EMPTY\_QUEUE

  The referenced queue is empty.

- VM:RETRY\_EXHAUSTED

  The maximum number of retries for the operation is reached.

- VM:CONNECTIVITY

  The connection is no longer valid. Apply a reconnection policy if defined in the application
  setup.

- VM:QUEUE\_TIMEOUT

  Timeout exceeded waiting for response on a queue.

- VM:PUBLISH\_CONSUMER\_FLOW\_ERROR

  The \*Publish consume\* operation failed to process the published message.

## See Also

- [VM Connector Reference](https://docs.mulesoft.com/vm-connector/latest/vm-reference)

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

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