---
schema_version: "1"
id: edf2b41685e20fa47b297c2dd3383c416ba5f76c66ce0a904761f30cf34e2469
title: Troubleshooting MongoDB Connector 6.3
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mongodb-connector/6.3/mongodb-connector-troubleshooting.md
canonical_url: https://docs.mulesoft.com/mongodb-connector/6.3/mongodb-connector-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 3ebad35f3025c2eedf40170a127c7bce81c649413d78203a1f8a3d6eae841af5
description: MuleSoft Documentation Site
release: "6.3"
latest: false
---
---
product: MongoDB Connector
version: 6.3
---

# Troubleshooting MongoDB Connector 6.3

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

To troubleshoot Anypoint Connector for MongoDB (MongoDB Connector), become familiar with the
information about interpreting commonly thrown exception messages.

## Enable SSL Logging

Enable SSL logs to investigate an issue related to TLS communications.

Set your SSL log level depending on your required level of detail:

1.  Enable only SSL log details:

    `javax.net.debug=ssl`

2.  Enable only handshaking details. (The handshake protocol is a series of messages exchanged over
    the record protocol.)

    `javax.net.debug=ssl:handshake`

3.  Enable handshaking details and SSL details at the same time:

    `javax.net.debug=ssl, handshake`

4.  Enable the dumping of all details and traffic data:

    `javax.net.debug=all`

    > [!NOTE] This option is very verbose and under normal circumstances is not necessary.

> [!WARNING] SSL logging results in a performance impact for HTTPS or other TLS connections. Enable
> SSL logging only to troubleshoot a specific issue and do not enable it for extended periods. SSL
> logging produces a significant amount of log messages and can inundate your log file if it is left
> enabled and unattended.

To enable SSL logs:

Set the debug parameter as an argument in the runtime configuration for the application.

1.  In Studio, right-click on the project and select **Run > Run Configurations**.

2.  Go to the **Arguments** tab and add `-M-Djavax.net.debug=ssl` in the **VM arguments** section.

## Enable Verbose Exception Logging

Enable verbose exception logs to show a complete stack trace of the error instead of the default
truncated output:

1.  In Studio, right-click on the project and select **Run > Run Configurations**.

2.  Go to the **Arguments** tab and append the arguments in the **VM arguments** section to add the
    `mule.verbose.exceptions` property. For example:

    `-XX:PermSize=128M -XX:MaxPermSize=256M -Dmule.verbose.exceptions=true`

## Enable Verbose Logging

To get a better understanding of why an application’s interaction with MongoDB Connector is failing,
temporarily enable verbose logging for the connector.

Remember to always disable enhanced verbosity after troubleshooting, because it can affect your Mule
application’s 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` folder.

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

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

    ```xml
    			<Loggers>
    				...
    				<AsyncLogger name="com.mulesoft.connectors.mongodb" 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 Commonly Thrown Exceptions

Here is a list of commonly thrown exception messages and how to interpret them:

- MONGO:CONNECTIVITY

  Either a connection could not be established or there is a connectivity error.

- MONGO:CONSISTENCY\_ERROR

  The data is not consistent because the client cannot find a read after performing a write.

- MONGO:DUPLICATE\_ERROR

  There is a duplicate key.

- MONGO:INVALID\_INPUT

  The provided input data for an operation is not valid.

- MONGO:NOT\_FOUND

  The server could not find the requested resource.

- MONGO:PERMISSIONS\_DENIED

  A permission error occurred while accessing a collection in a database.

- MONGO:RETRY\_EXHAUSTED

  The maximum number of retries for the operation is reached.

- MONGO:TIMEOUT

  A specific request takes longer than the configuration timeout values.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [MongoDB Connector Reference](https://docs.mulesoft.com/mongodb-connector/6.3/mongodb-connector-reference)

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

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