---
schema_version: "1"
id: ce286fc04294b125f820c6c65221abd41b5d0a85b5dff0b1d41d332f6ef7ba3a
title: Testing a Connection Configuration
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/int-configure-components-check-connection.md
canonical_url: https://docs.mulesoft.com/anypoint-code-builder/int-configure-components-check-connection
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 4d623c0c4f33899d680d6cf75e4dccd500a63d2c158741009f135d7397699cac
description: MuleSoft Documentation Site
latest: true
---
---
product: Anypoint Code Builder
version: master
---

# Testing a Connection Configuration

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

Most connectors provide an operation, such as the HTTP Listener operation, that triggers the flow to
start. These operations typically include connection configurations that you can test.

## Test Connection from the Configuration Panel

You can test the connection from the connectors **Configuration** panel. For example, to test an
HTTP Listener connection:

![Configuration panel for connectors](/mulesoft/current/en-us/anypoint-code-builder/_images/acb-configuration-panel-test.png)

<table><tbody><tr><td><i data-value="1"></i><b>1</b></td><td>Click the <strong>+</strong> icon on the connector to open the configuration panel.</td></tr><tr><td><i data-value="2"></i><b>2</b></td><td>After filling in the required fields, click <strong>Test Connection</strong>.</td></tr></tbody></table>

The status bar shows the progress:

- **Verifying connection** indicates that the test is in progress.

- **Connection is valid** indicates a successful connection.

- **Invalid Connection Got status code: 500 when trying to resolve a Mule Runtime operation**
  indicates a connection error.

## Test Connection from the Code Editor

You can test the connection from the code editor. For example, to test an HTTP Listener connection,
click **Test Connection** in the code editor:

![HTTP Listener Test Connection link in the code editor](/mulesoft/current/en-us/anypoint-code-builder/_images/http-listener-test-connection.png)

The status bar shows the progress:

- **Verifying connection inbound-request** indicates that the test is in progress.

- **Connection is valid** indicates a successful connection.

- **Invalid Connection Got status code: 500 when trying to resolve a Mule Runtime operation**
  indicates a connection error.

  A common code `500` error is `port 8081: Address already in use`. For port conflicts, configure a
  different port, such as `8082`, and retest the connection.

Before publishing, run your application in debug mode.