---
schema_version: "1"
id: 2bb5f9cee2ef78e2e387ca4bf435e14ad4f42390f6871dbfa15d6111d5ec6c15
title: Troubleshooting Sockets Connector
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/sockets-connector/latest/sockets-connector-troubleshooting.md
canonical_url: https://docs.mulesoft.com/sockets-connector/latest/sockets-connector-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: db7ffec87c3e3732c6397dfea3ff09598cf3f2e6b8aa145ce4a169b21dcea35c
description: MuleSoft Documentation Site
release: "1.2"
latest: true
---
---
product: Sockets Connector
version: 1.2
is-latest-version: true
---

# Troubleshooting Sockets Connector

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

To troubleshoot Anypoint Connector for Sockets (Sockets 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 Sockets Connector is
failing, temporarily enable verbose logging for the 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.extension.socket" 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:

- SOCKETS:UNKNOWN\_HOST

  Mule cannot determine the IP address of a host.

- SOCKETS:CONNECTIVITY

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

- SOCKETS:CONNECTION\_TIMEOUT

  The attempt to connect to the Socket timed out.

- SOCKETS:RETRY\_EXHAUSTED

  The maximum number of retries for the operation is reached.

- SOCKETS:LENGTH\_EXCEEDED

  There was an attempt of reading or writing more bytes than the allowed limit.

## See Also

- [Sockets Connector Reference](https://docs.mulesoft.com/sockets-connector/latest/sockets-documentation)

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

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